pgn
July 03, 2012 02:12PM
Sorry, I don't understand your point.

Why is this ok, and fully functional?
---------------------------------
server { server_name test1.loc;
listen 10.0.0.1:443;
...
server {server_name test2.loc;
listen 10.0.0.1:443;
...
---------------------------------

but this is not?
---------------------------------
server { server_name test1.loc;
listen [2001:xxx:xxxx:xxx::1]:443 ipv6only=on;
...
server {server_name test2.loc;
listen [2001:xxx:xxxx:xxx::1]:443 ipv6only=on;
...
---------------------------------


In BOTH cases, BOTH server{} are listening on the same address:port, differentiated by server_name for vhost redirection.
Subject Author Posted

startup error -> "[emerg] duplicate listen options" if 2nd IPv6 listener is enabled

pgn July 03, 2012 01:39PM

Re: startup error -> "[emerg] duplicate listen options" if 2nd IPv6 listener is enabled

Oleksandr V. Typlyns'kyi July 03, 2012 02:04PM

Re: startup error -> "[emerg] duplicate listen options" if 2nd IPv6 listener is enabled

pgn July 03, 2012 02:12PM

Re: startup error -> "[emerg] duplicate listen options" if 2nd IPv6 listener is enabled

Oleksandr V. Typlyns'kyi July 03, 2012 02:36PM

Re: startup error -> "[emerg] duplicate listen options" if 2nd IPv6 listener is enabled

pgn July 03, 2012 03:04PM

Re: startup error -> "[emerg] duplicate listen options" if 2nd IPv6 listener is enabled

Oleksandr V. Typlyns'kyi July 03, 2012 03:24PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 307
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready