NGINX fails to install/upgrade if IPv6 is completely disabled.

Bug #1743592 reported by Thomas Ward on 2018-01-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Low
Thomas Ward

Bug Description

There is a known issue where NGINX will not properly run or install when IPv6 is fully disabled on a system.

Per Bug #1712696 which first detailed this, these are some 'relevant' log entries:

Aug 23 23:52:24 thomas-ThinkPad-T430 nginx[20166]: nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
Aug 23 23:52:24 thomas-ThinkPad-T430 nginx[20166]: nginx: configuration file /etc/nginx/nginx.conf test failed
Aug 23 23:52:24 thomas-ThinkPad-T430 systemd[1]: nginx.service: Control process exited, code=exited status=1
Aug 23 23:52:24 thomas-ThinkPad-T430 systemd[1]: Failed to start A high performance web server and a reverse proxy server.

As you can see the system could not bind to Port 80 on IPv6.

While this is a **nonstandard** setup, there are some systems which are configured to not have IPv6 support. It should currently be considered whether we should test for such 'systems' to see whether IPv6 is enabled or not, and modify the configuration file accordingly during install/configure.

This issue happens regardless of the 'supported' operating system status or not, and is a core NGINX package issue, but also a core 'incompatible configuration' issue with systems which disable IPv6.

Thomas Ward (teward) on 2018-01-16
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers