Replies: 1 comment 2 replies
-
Hi! Sorry about this issue. I think this is a duplicate of #110. We are tracking it there. I would ask you: is your VPS dual stack? Does it have an IPV6 address? Otherwise there might be some nat funniness going on for your v6 host to address it maybe? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I’ve got a Pangolin setup running on a VPS, installed using the standard install script. It includes Traefik with the CrowdSec and GeoBlock plugins. My local server is connected to the system via a Newt tunnel. Everything was deployed as per the Pangolin docs. The Docker’s internal network appears to be IPv4-only (there’s no daemon.json).
Public access to services exposed by Pangolin works via both IPv4 and IPv6.
For IPv4 requests, I can see the real client IP correctly in the X-Real-IP and X-Forwarded-For headers.
For IPv6 requests, however, those headers always show the internal IPv4 address of the container (e.g. 172.22.0.1).
So far, I’ve never seen an IPv6 address appear in Traefik’s logs or in the GeoBlock plugin’s output.
This raises a couple of questions:
I’m happy to provide further config details if needed.
I'm not a professional sysadmin, just a home network user trying to understand how Pangolin handles IPv6 internally. Please let me know if I’m misunderstanding how the pieces fit together.
Thanks in advance!
4ndreasH
Beta Was this translation helpful? Give feedback.
All reactions