[GH-ISSUE #2884] ipv6 - fatal crash when not enabled #1975

Closed
opened 2026-02-26 07:33:32 +03:00 by kerem · 3 comments
Owner

Originally created by @webspes on GitHub (May 4, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2884

Describe the bug

Host of the VM does not have IPv6 and container don't have IPv6. Everything appears to starts, but after finding the logs, the logs says this and no service (80, 81,443) even on IPv4:

data/logs/fallback_error.log

2023/05/04 22:27:45 [emerg] 4414#4414: socket() [::]:80 failed (97: Address family not supported by protocol)

It is fixed in nginx-builds 2 years ago it seems. The problem is that nginx tries to bind to ipv6, but fails.

I have no known workarounds. The docker-compose file says:

Uncomment this if IPv6 is not enabled on your host

DISABLE_IPV6: 'true'

However, this is not supported:
validating /home/docker-compose.yml: services.app Additional property DISABLE_IPV6 is not allowed

OS: Rocky Linux 9.1 lxc container running on ProxMox host.

Originally created by @webspes on GitHub (May 4, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2884 **Describe the bug** Host of the VM does not have IPv6 and container don't have IPv6. Everything appears to starts, but after finding the logs, the logs says this and no service (80, 81,443) even on IPv4: data/logs/fallback_error.log 2023/05/04 22:27:45 [emerg] 4414#4414: socket() [::]:80 failed (97: Address family not supported by protocol) It is fixed in nginx-builds 2 years ago it seems. The problem is that nginx tries to bind to ipv6, but fails. I have no known workarounds. The docker-compose file says: # Uncomment this if IPv6 is not enabled on your host DISABLE_IPV6: 'true' However, this is not supported: validating /home/docker-compose.yml: services.app Additional property DISABLE_IPV6 is not allowed OS: Rocky Linux 9.1 lxc container running on ProxMox host.
kerem 2026-02-26 07:33:32 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@paaatcha commented on GitHub (Nov 20, 2023):

I was facing the same problem and found the solution on issue #473

<!-- gh-comment-id:1819378919 --> @paaatcha commented on GitHub (Nov 20, 2023): I was facing the same problem and found the solution on issue #473
Author
Owner

@github-actions[bot] commented on GitHub (Jun 6, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2151261557 --> @github-actions[bot] commented on GitHub (Jun 6, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Jun 9, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2954463150 --> @github-actions[bot] commented on GitHub (Jun 9, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1975
No description provided.