Following the Docker Compose setup guide traefik doesn't reveal the client's IPv6 Addresses within logs if requests are performed with native IPv6 only.
This is causing Problems with GeoIP based rules (blocked in my case) and showing wrong IP-Adresses within the Access-Logs (see screenshots attached)
Traefik logs also recorded the internal docker gateway address (172.18.0.1 in this case) - the internal GW address have been confirmed by docker network inspect pangolin (renamed default network according to guide).
Please update docs containing the solution below or ask me to create a PR for the docs.
Environment
OS Type & Version: Rocky Linux 9.7 (Blue Onyx)
Pangolin Version: 1.14.1
Gerbil Version: latest
Traefik Version: 3.4.0
Newt Version: N/A
Olm Version: (if applicable)
To Reproduce
Manual Docker Compose setup with IPv6 enabled host (but not docker network) and clients requesting IPv6 only (IPv4 disabled).
Expected Behavior
Traefik to show Client's real IPv6 Addresses instead of the internal docker networks gateway address.
This can be achieved by enabling IPv6 within the docker network as following:
networks:
default:
driver: bridge
name: pangolin
enable_ipv6: true # Uncomment if host uses native IPv6 and AAAA DNS records for the pangolin domain are set
after this change Traefik was enable to record the native IPv6, not the internal IPv4 NAT Docker Gateway Address.
Originally created by @doschn on GitHub (Dec 28, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2175
### Describe the Bug
Following the [Docker Compose setup guide](https://docs.pangolin.net/self-host/manual/docker-compose) traefik doesn't reveal the client's IPv6 Addresses within logs if requests are performed with native IPv6 only.
This is causing Problems with GeoIP based rules (blocked in my case) and showing wrong IP-Adresses within the Access-Logs (see screenshots attached)
<img width="1565" height="735" alt="Image" src="https://github.com/user-attachments/assets/e1b711b9-0f01-4b45-91ea-1967d01d87ba" />
<img width="1534" height="480" alt="Image" src="https://github.com/user-attachments/assets/d8c46053-fdcf-4593-8952-cd4059b6ded2" />
Traefik logs also recorded the internal docker gateway address (172.18.0.1 in this case) - the internal GW address have been confirmed by `docker network inspect pangolin` (renamed default network according to guide).
Please update docs containing the solution below or ask me to create a PR for the docs.
### Environment
- OS Type & Version: Rocky Linux 9.7 (Blue Onyx)
- Pangolin Version: 1.14.1
- Gerbil Version: latest
- Traefik Version: 3.4.0
- Newt Version: N/A
- Olm Version: (if applicable)
### To Reproduce
Manual Docker Compose setup with IPv6 enabled host (but not docker network) and clients requesting IPv6 only (IPv4 disabled).
### Expected Behavior
Traefik to show Client's real IPv6 Addresses instead of the internal docker networks gateway address.
This can be achieved by enabling IPv6 within the docker network as following:
```
networks:
default:
driver: bridge
name: pangolin
enable_ipv6: true # Uncomment if host uses native IPv6 and AAAA DNS records for the pangolin domain are set
```
after this change Traefik was enable to record the native IPv6, not the internal IPv4 NAT Docker Gateway Address.
<img width="1519" height="373" alt="Image" src="https://github.com/user-attachments/assets/35acf2b2-ea13-40a0-bb50-f47dbfd7f847" />
accidentally closed by comment of a commit in my private repo containing a fixed compose file.
<!-- gh-comment-id:3695024279 -->
@doschn commented on GitHub (Dec 28, 2025):
accidentally closed by comment of a commit in my private repo containing a fixed compose file.
@AstralDestiny commented on GitHub (Dec 29, 2025):
It's due to some badger stuff, Both devs have been bugged by me for a while now for fixing ipv6 issues. However backend services are not affected. The enable_ipv6 should be there it has to be there either way as most aren't running with full ipv6 on the daemon. Which at the same time can cause some issues if you use any vpn containers as they don't know how to handle v6 so it just complains.
<!-- gh-comment-id:3696584601 -->
@AstralDestiny commented on GitHub (Dec 29, 2025):
It's due to some badger stuff, Both devs have been bugged by me for a while now for fixing ipv6 issues. However backend services are not affected. The enable_ipv6 should be there it has to be there either way as most aren't running with full ipv6 on the daemon. Which at the same time can cause some issues if you use any vpn containers as they don't know how to handle v6 so it just complains.
@github-actions[bot] commented on GitHub (Jan 13, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
<!-- gh-comment-id:3741180853 -->
@github-actions[bot] commented on GitHub (Jan 13, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
Anybody help me solving the issue of getting docker pangolin network gateway IP in dashboard.
<!-- gh-comment-id:3770647996 -->
@usmandilmeer commented on GitHub (Jan 20, 2026):
Anybody help me solving the issue of getting docker pangolin network gateway IP in dashboard.
Anybody help me solving the issue of getting docker pangolin network gateway IP in dashboard.
Try to add ipv6 to the network configuration in the compose file as follows (see initial issue):
enable_ipv6: true
<!-- gh-comment-id:3771072900 -->
@doschn commented on GitHub (Jan 20, 2026):
> Anybody help me solving the issue of getting docker pangolin network gateway IP in dashboard.
Try to add ipv6 to the network configuration in the compose file as follows (see initial issue):
```
enable_ipv6: true
```
@github-actions[bot] commented on GitHub (Feb 4, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
<!-- gh-comment-id:3844570188 -->
@github-actions[bot] commented on GitHub (Feb 4, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Feb 20, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
<!-- gh-comment-id:3930918837 -->
@github-actions[bot] commented on GitHub (Feb 20, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Mar 6, 2026):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
<!-- gh-comment-id:4008717747 -->
@github-actions[bot] commented on GitHub (Mar 6, 2026):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @doschn on GitHub (Dec 28, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2175
Describe the Bug
Following the Docker Compose setup guide traefik doesn't reveal the client's IPv6 Addresses within logs if requests are performed with native IPv6 only.
This is causing Problems with GeoIP based rules (blocked in my case) and showing wrong IP-Adresses within the Access-Logs (see screenshots attached)
Traefik logs also recorded the internal docker gateway address (172.18.0.1 in this case) - the internal GW address have been confirmed by
docker network inspect pangolin(renamed default network according to guide).Please update docs containing the solution below or ask me to create a PR for the docs.
Environment
To Reproduce
Manual Docker Compose setup with IPv6 enabled host (but not docker network) and clients requesting IPv6 only (IPv4 disabled).
Expected Behavior
Traefik to show Client's real IPv6 Addresses instead of the internal docker networks gateway address.
This can be achieved by enabling IPv6 within the docker network as following:
after this change Traefik was enable to record the native IPv6, not the internal IPv4 NAT Docker Gateway Address.
@doschn commented on GitHub (Dec 28, 2025):
accidentally closed by comment of a commit in my private repo containing a fixed compose file.
@AstralDestiny commented on GitHub (Dec 29, 2025):
It's due to some badger stuff, Both devs have been bugged by me for a while now for fixing ipv6 issues. However backend services are not affected. The enable_ipv6 should be there it has to be there either way as most aren't running with full ipv6 on the daemon. Which at the same time can cause some issues if you use any vpn containers as they don't know how to handle v6 so it just complains.
@github-actions[bot] commented on GitHub (Jan 13, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@usmandilmeer commented on GitHub (Jan 20, 2026):
Anybody help me solving the issue of getting docker pangolin network gateway IP in dashboard.
@doschn commented on GitHub (Jan 20, 2026):
Try to add ipv6 to the network configuration in the compose file as follows (see initial issue):
@github-actions[bot] commented on GitHub (Feb 4, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Feb 20, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Mar 6, 2026):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.