mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 09:55:51 +03:00
[GH-ISSUE #1606] ipv6 not working with NPM in Docker #1204
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1204
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @swoop124 on GitHub (Nov 20, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1606
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
til now i only used ipv4 and npm was working fine, even with an Access List. Now i am beginning to switch to ipv6.
When no Acces List is set, NPM works fine with ipv6. But when i activate an Access List, i get a 403 Forbidden. Even when i allow my ipv6 Subnet in the Access List.
Nginx Proxy Manager Version
v2.9.12
To Reproduce
Steps to reproduce the behavior:
Expected behavior
open the Website even when coming from ipv6, only if in access list allowed
Screenshots
my Access List
Operating System
nmp is installed on a debian 10 (buster 10.10) in docker 20.10.8, build 3967b7d with enabled ipv6
Additional context
For testing i installed nmp on a alpine Proxmox LXC, with the same Access List. There it was working like a charme.
I found out, that when i am coming from a ipv6 subnet, then this ipv6 IP is natted to a Docker-Internal ipv4 address. Even within a internal ipv6 network it is natted to a internal ipv6-address.
@chaptergy commented on GitHub (Nov 21, 2021):
https://github.com/jc21/nginx-proxy-manager/issues/1105#issuecomment-950384265 might help
@swoop124 commented on GitHub (Nov 22, 2021):
hi an thanks for the suggession, but no, it isn't helping.
still same message in log:
[22/Nov/2021:08:24:02 +0000] - - 403 - GET https sub.domain.com "/" [Client 172.18.0.1] [Length 111] [Gzip 1.35] [Sent-to host] "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:94.0) Gecko/20100101 Firefox/94.0" "-"
[22/Nov/2021:08:24:02 +0000] - - 403 - GET https sub.domain.com "/favicon.ico" [Client 172.18.0.1] [Length 111] [Gzip 1.35] [Sent-to host] "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:94.0) Gecko/20100101 Firefox/94.0" "https://sub.domain.com/"
I am coming from an ipv6 ip-address.
@swoop124 commented on GitHub (Nov 27, 2021):
no one else?
@Saik0Shinigami commented on GitHub (Dec 10, 2021):
From my understanding the Docker gateway is converting IPv6 traffic to IPv4, thus why you see 172.18.0.1 as your client.
I'm in the same boat and have yet to find a functional solution.
(Aside from host mode networking that is.)
@swoop124 commented on GitHub (Dec 10, 2021):
yes you are right. why npm-docker is doing that, i dont know.
my solution is, i use an alpine linux VM/LXC. With that it is working and ipv4 and ipv6 are working.
as soon as i have my setup running, i can report.
regards
@swoop124 commented on GitHub (Dec 21, 2021):
ok.
i've installed a complet new alpine-lxc on my Proxmox Server and deployed npm.
now it is working as expected. even with ipv6.
the only problem was, that i had to configure all my domains an certificates once again, so it would be very goot, if there is a export and import funktionality.
regards
@Intenos commented on GitHub (Dec 27, 2021):
I believe I have also an issue with jc21/nginx-proxy-manager and ipv6.
I have setup a reverse proxy for Nextcloud (besides others). Everything works well, except of the Nextcloud Android App used remotely, not via the local WIFI. I know that this is related to ipv6 as I already had an issue with it about one year ago which I fixed by properly setting up the ipv6 routing in my router (Fritz!Box). Any issue there I can exclude as route case and clearly link it to the Nginx-Proxy-Manager as everything works when disabling NPM and setting up a reverse proxy via the local Nginx of my openmediaVault system.
However, this I did only for testing as I there miss the auto-generated LetsEntscrypt certificate. Therefore I hope that anybody can help with a solution.
@Intenos commented on GitHub (Dec 27, 2021):
I just found that it works with jlesage/nginx-proxy-manager.
@github-actions[bot] commented on GitHub (Mar 1, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 14, 2025):
Issue was closed due to inactivity.