Docker Compose setup: Native IPv6 #424

Closed
opened 2026-04-05 17:09:44 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @doschn on 12/28/2025

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)

Image Image

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.

Image
*Originally created by @doschn on 12/28/2025* ### 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" />
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#424