IPv4 & IPv6 combination

I have a virtual server with Debian Wheezy and nginx 1.4.4 installed: nginx version: nginx/1.4.4 TLS SNI support enabled configure arguments: --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http-client-body-temp-path=/var/lib/nginx/body --htt

Re: IPv4 & IPv6

On Apr 7, 2013, at 0:44 , Jim Ohlstein wrote: > This way there is no competition for what is listening on IPv6 addresses > and you should not see that error. I've been doing it this way for at > least a couple of years now, certainly before 1.0.x series came out. It > may not be the "recommended"

Re: IPv4 & IPv6

Thanks Maxim ! There was a misunderstanding there, I thought I shouldn't use the whole directive, I didn't get that only the 'ipv6only=on' part was not to be repeated amongst servers. Works great ('of course it does!' ;o)). Thanks for the help again, --- *B. R.* On Sat, Apr 6, 2013 at 5:25 PM,

Re: IPv4 & IPv6

Hello! On Sat, Apr 06, 2013 at 04:05:22PM -0400, B.R. wrote: > That's exactly what I tried first, and if there are multiple servers > listening to same ports, I get the following error: > nginx: [emerg] duplicate listen options for [::]:80 in > /etc/nginx/conf.d/***.conf:3 You've already been to

Re: IPv4 & IPv6

On 4/6/13 4:05 PM, B.R. wrote: > That's exactly what I tried first, and if there are multiple servers > listening to same ports, I get the following error: > nginx: [emerg] duplicate listen options for [::]:80 in > /etc/nginx/conf.d/***.conf:3 > See follow-up messages or (through the forum archive

Re: IPv4 & IPv6

That's exactly what I tried first, and if there are multiple servers listening to same ports, I get the following error: nginx: [emerg] duplicate listen options for [::]:80 in /etc/nginx/conf.d/***.conf:3 See follow-up messages or (through the forum archive on this subject): http://forum.nginx.org/

Re: IPv4 & IPv6

server { listen 80; listen [::]:80 ipv6only=on; server_name one; ... } server { listen 443 ssl; listen [::]:443 ssl ipv6only=on; server_name one; ... } -- Igor Sysoev http://nginx.com/services.html On Apr 6, 2013, at 19:01 , B.R. wrote: > Add-on: > >

Re: IPv4 & IPv6

Add-on: Besides, as I explained earlier, having generic 'listen' directives implies some difficulties. For example, I am using 2 virtual servers to serve content for the same server_name, one listening on port 80, the other on port 443, allowing me to serve cotnent for HTTP and HTTPS in different

Re: IPv4 & IPv6

But as I noticed earlier, these configuration directives conflict with each other across multiple virtual servers... That's a huge step backwards. H ​aving to specify them only once across every configuration file is counter-intuitive. Why isn't nginx able to ​summarize all the needs for listening

Re: IPv4 & IPv6

Hello! On Sat, Apr 06, 2013 at 02:25:54AM -0400, B.R. wrote: > Hello, > > It seems I solved the problem... > It was indeed by reading a little more carefully the doc > http://wiki.nginx.org/HttpCoreModule#listen, thanks @Lukas! ;o) > > The '*:80' syntax is used for IPv4 listening, I don't under

Re: IPv4 & IPv6

Hello, It seems I solved the problem... It was indeed by reading a little more carefully the doc http://wiki.nginx.org/HttpCoreModule#listen, thanks @Lukas! ;o) The '*:80' syntax is used for IPv4 listening, I don't understand why it works as-is for you Ted. Maybe Maxim will be of a better help on

Re: IPv4 & IPv6

Hmm... @Maxim I guess I haven't understood your piece of advice, since 'listen' can only be used in 'server' directive... What is it you wanted me to try, again? :oD --- *B. R.* On Fri, Apr 5, 2013 at 8:02 PM, B.R. wrote: > I have indeed several virtual servers. > > I have a specific one which

Re: IPv4 & IPv6

I have indeed several virtual servers. I have a specific one which serves different content whether a client connects in HTTP or HTTPS (basically the HTTP content provides directions for the HTTPS setup). I also have one virtual server which I want listening on IPv4 only, not IPv6. That's why I p

Re: IPv4 & IPv6

On Apr 5, 2013, at 6:07 PM, B.R. wrote: > @Ted > I​ tested your solution but as I expected nginx is only listening on IPv4 > interfaces after restart and not IPv6 ones anymore.​ Weird. I have this: listen 443 ssl; listen [::]443 ipv6only=on ssl; But aside from

Re: IPv4 & IPv6

Hello! On Fri, Apr 05, 2013 at 06:07:23PM -0400, B.R. wrote: > Hello, > > @Maxim > I tried the duplicate configuration entries: > listen 80; > listen [::]:80 ipv6only=on; > > I has the following error: > nginx: [emerg] duplicate listen options for [::]:80 in > /etc/nginx/conf.d/***.conf:3 If y

Re: IPv4 & IPv6

Hello, @Maxim I tried the duplicate configuration entries: listen 80; listen [::]:80 ipv6only=on; I has the following error: nginx: [emerg] duplicate listen options for [::]:80 in /etc/nginx/conf.d/***.conf:3 @Ted I​ tested your solution but as I expected nginx is only listening on IPv4 interfac

RE: IPv4 & IPv6

Everything you need to know: http://nginx.org/en/docs/http/ngx_http_core_module.html#listen ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: IPv4 & IPv6

On Apr 5, 2013, at 4:17 PM, "B.R." wrote: > Is there any other way to allow Nginx ot listen on both interface types > without mandatory system configuration? I just have "listen *:80" in my configurations, and it works fine over IPv4 and IPv6. ___ ng

Re: IPv4 & IPv6

Hello! On Fri, Apr 05, 2013 at 04:17:09PM -0400, B.R. wrote: > Hello, > > I noticed in an article dedicated to the subject > (Fr)that > to allow Nginx to listen both on IPv4 and IPv6 interfaces > simultaneously, you needed to

IPv4 & IPv6

Hello, I noticed in an article dedicated to the subject (Fr)that to allow Nginx to listen both on IPv4 and IPv6 interfaces simultaneously, you needed to set sysctl with the following configuration (otherwise Nginx listening bin