AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Bugs

Self-hosted Docker IPv6 Forwarding Support

(#825) Bug Needs triage self-hosting
by RexSystem originally by @Yamada993 on GitHub

Observed behaviour

In a network environment where both IPv4 and IPv6 are enabled, if a user accesses a self-hosted instance via IPv6, the reported IP address in the background is the private IPv4 gateway of Docker, rather than the actual user's IPv6 address. Users do not encounter this issue when using IPv4.

Reproduction steps

  1. Configure self-hosting using Docker
  2. Users access the Web using IPv6
  3. The administrator panel shows that the user's IP is the private IPv4 gateway of Docker, rather than the user's actual IPv6 address.

Build information

Stable Web 2026.903.25301, Windows NT 10.0 (x64), Chrome 152.0.0.0, Locale en-GB

Platform

Self-hosting

Evidence

image
  • 648283139-c0471747-d1a3-4032-b31c-2f11ba7bc0ef.png

    648283139-c0471747-d1a3-4032-b31c-2f11ba7bc0ef.png

    298×46 | 2 kB

1 comment

Sign in with Fluxer to comment and vote.
Comment by @Yamada993
RexSystem 1 vote originally by @Yamada993 on GitHub OP
Just need to modify the "network" section of the docker compose file, and you can see the real IPv6 address of the user. 
networks:
  fluxer:
    driver: bridge
    enable_ipv6: true
    ipam:
      config:
        - subnet: fd12:3456:789a:1::/64
Permalink