** Changed in: nginx (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818574
Title:
Nginx cannot bind static IPv6 address on boot
To manage notifications
** Changed in: nginx (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818574
Title:
Nginx cannot bind static IPv6 address on boot
To manage notifications about
Thank you Andreas, thank you Thomas, the workaround to depend on
network-online.target is fine for me.
I agree with Thomas that freebinding is not the appropriate way to cope
with binding to address that should deterministically be present on
start of the service.
You have surely made all the det
Note that this type of "free binding" behavior is not desirable in MOST
setups. Discussing in the Ubuntu Server IRC channel, in MOST setups, if
you can't do something like bind to an IP it should error; slow-to-
configure IPv6 aside, the most desirable thing would be for improper
IP/bind configura
I found this thread:
https://forum.nginx.org/read.php?29,248807,248807#msg-248807
Looks like something similar was proposed already, but not applied. This
thread also had a discussion: http://mailman.nginx.org/pipermail/nginx-
devel/2014-March/005138.html
** Changed in: nginx (Ubuntu)
Sta
Thanks for filing this bug in Ubuntu.
There are similar cases out there with other services, when a specific
IP address is selected for the service to bind to. openssh, for example,
has this bug upstream: https://bugzilla.mindrot.org/show_bug.cgi?id=2512
A few solutions, or workarounds, exist for
