*** This bug is a duplicate of bug 1743592 ***
https://bugs.launchpad.net/bugs/1743592
** Bug watch added: Debian Bug tracker #942817
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942817
** Also affects: nginx (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942817
*** This bug is a duplicate of bug 1743592 ***
https://bugs.launchpad.net/bugs/1743592
** This bug has been marked a duplicate of bug 1743592
NGINX fails to install/upgrade if IPv6 is completely disabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
ahasenack:
Yeah, no need to triage further, this alone is a Won't Fix for SRUing
unless we need to push another fix out and include this and others along
with it.
Users running into this issue can easily fix this by commenting out that
line that's listening on v6.
** Changed in: nginx
Sta
** Also affects: nginx
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838246
Title:
Nginx 1.14.0 fails to start if ipv6 support on host is disabled
To ma
@teward, feel free to triage further, my initial concern here was that
this was a regression introduced in an SRU, but that doesn't seem to be
the case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
So to clarify, this is not a regression introduced in an SRU, this
configuration has been part of nginx for years now in Ubuntu.
** Tags removed: dist-upgrade
** Changed in: nginx (Ubuntu)
Status: Incomplete => Triaged
** Changed in: nginx (Ubuntu)
Importance: Undecided => Low
--
You
Hi.
It's a standard setup on our corporate LAN/WAN where our Information,
Network and Data Security team mandate that IPv6 is disabled across the
board.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
This has been reported before I have to find the bug but IPv6 disabled
fully including link local is not a standard setup, I dont think an SRU
will fix this since config files are usually not updated by an SRU.
Even if we patch this the config file will need manually updated by end
users to adjust
I just disbaled ipv6 on a plain bionic system, with the released package
of nginx (no updates), and nginx fails to start with the same error, so
this is not a regression introduced in a bionic update:
root@bionic-nginx:~# service nginx status
● nginx.service - A high performance web server and a r
Thanks for filing this bug in Ubuntu.
I installed nginx 1.14.0-0ubuntu1 from the release pocket of Bionic, i.e., no
updates:
root@bionic-nginx:~# apt-cache policy nginx
nginx:
Installed: 1.14.0-0ubuntu1
Candidate: 1.14.0-0ubuntu1
Version table:
*** 1.14.0-0ubuntu1 500
500 http://br
10 matches
Mail list logo
