Hey, I've found older Messages about IPv6 support in this List that its not supported right now, so my Question is there any plan to implement it soon? Greetings Tobias
on 2009-02-10 22:30
on 2009-04-23 02:58
On Tue, Apr 21, 2009 at 07:17:23PM -0400, r wrote: > After modifying the configuration file with this line in a server section: > > > listen [::]:80 > > > I tested it with nginx -t before loading it: > > > the configuration file /etc/nginx/nginx.conf syntax is ok > the configuration file /etc/nginx/nginx.conf was tested successfully If you run nginx on Linux, then: $grep 98 /usr/include/asm-generic/errno.h #define EADDRINUSE 98 /* Address already in use */ There is another process that run on this port. As to "-t", nginx ignores EADDRINUSE while testing, because testing is usually done when nginx is already listening. However, it's strange, that nginx did not log the text error description. What OS do you use ?
on 2009-04-23 15:43
On Wed, Apr 22, 2009 at 02:12:15PM -0400, r wrote: > tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 9810/nginx.conf-ipv4 > # nginx -c nginx.conf-ipv6 > So, it works, but impossible to have two listen entries with both ipv4 and ipv6 (like the one in the post you made in february). > > I'm running Debian GNU/Linux 5.0 (lenny). It seems in Linux [::]:443 listens on both IPv6 and IPv4 addresses. You may test this by making a request to IPv4 address, it should work. If you want to set two listen sockets, then you need listen [::]:443 default ipv6only=on; listen [::]:80;