The issue is with this:
[150] # service nginx restart
Stopping nginx:[FAILED]
Since stopping FAILED, the IP/port still in use. That's why start failed
with "binding" error.
You can try "service nginx stop" along and check error log to see why it
faile
I believe this is related to blocking neighbor discovery on the address for
the purposes of doing direct server return load balancing, and not nginx
related, thanks!
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,280234,280239#msg-280239
___
OK, that's odd: I commented out the ipv4 address and it still fails. It's
not a conflict then, so something's odd in the network stack...
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,280234,280238#msg-280238
___
nginx mailing list
nginx@n
Yup:
eth0 Link encap:Ethernet HWaddr 00:50:56:8C:62:77
inet addr:207.55.17.91 Bcast:207.55.19.255 Mask:255.255.252.0
inet6 addr: fe80::250:56ff:fe8c:6277/64 Scope:Link
inet6 addr: 2607:f678::17:79/64 Scope:Global
inet6 addr: 2607:f678::17:91/64 Sco
I've no problem with IPv6 on my server using specific v4 and v6 listen
statements.
Is the IP you're trying to use actually configured on an interface?
Steve.
On 21/06/2018 21:37, abatie wrote:
I have nginx binding to a variety of addresses for ssl and target selection
reasons. Now I'm trying
I have nginx binding to a variety of addresses for ssl and target selection
reasons. Now I'm trying to add ipv6 support. Since I'm using specific
listen addresses, I wouldn't expect to have a binding conflict, however I
am, and I'm hoping someone can point me in the right direction:
server {
