Feature request: Keep IPv6 address for ProtonVPN servers

[ranile]

What's the feature 🧐

ProtonVPN has servers that can be reached over IPv6, however these addresses are discarded somewhere during the server address collection stage. It would be nice to give gluetun no IPv4 WAN and still be able to reach ProtonVPN (which also provides v6 connectivity over the tunnel)

Extra information and references

$ sudo docker exec -it gluetun cat /gluetun/servers/protonvpn.json | grep '::'
# nothing

$ sudo docker exec -it gluetun cat /gluetun/servers/mullvad.json | grep '::'
        "2a04:27c0:0:c::f001"
# ... a lot of addresses
$ $ sudo docker exec -it gluetun cat /gluetun/servers/airvpn.json | grep '::'
        "2001:ac8:29:5::2"
# ... more addresses

The URL for fetching servers with v6 appears to be: https://account.protonvpn.com/api/vpn/v1/logicals?WithIpV6=1, based on network inspection of their download page. Unless another change is needed downstream, the only source change required here is to update the URL at

gluetun/internal/provider/protonvpn/updater/api.go

Line 571 in c12824d

const url = "https://account.proton.me/api/vpn/logicals"

and read EntryIPv6 for servers that do have it when parsing the API response into

[github-actions]

@qdm12 is more or less the only maintainer of this project and works on it in his free time.
Please:

• do not ask for updates, be patient
• 👍 the issue to show your support instead of commenting
  @qdm12 usually checks issues at least once a week, if this is a new urgent bug,
  revert to an older tagged container image

[ranile]

I tested this with custom provider and it works well. No leaks

compose.yaml

networks:
  gluetun6:
    enable_ipv4: false
    enable_ipv6: true

services:
  gluetun:
    image: qmcgaw/gluetun
    container_name: gluetun6
    sysctls:
      - net.ipv6.conf.all.disable_ipv6=0
    networks:
      - gluetun6
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun:/dev/net/tun
    volumes:
      - "./wg0.conf:/gluetun/wireguard/wg0.conf:ro"
    environment:
      - VPN_SERVICE_PROVIDER=custom
      - VPN_TYPE=wireguard

Where wg0.conf sets:

[Peer]
PublicKey = SG-71
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = [2a02:6ea0:d101:2282::10]:51820
PersistentKeepalive = 25

$ sudo docker run --rm --network=container:gluetun6 alpine sh -c "apk add curl && curl -4 https://ifconfig.me/ip"
# returns Proton's v4
$ sudo docker run --rm --network=container:gluetun6 alpine sh -c "apk add curl && curl -6 https://ifconfig.me/ip"
# returns Proton's v6

Integration with ProtonVPN would mean that features like port forwarding also work

[github-actions]

Closed issues are NOT monitored, so commenting here will likely NOT be seen.
If you think this is still unresolved and have more information to bring, please either
re-open this issue or create another issue.

❤️😠 temporarily help the Gluetun community and fight the AI slop scam website gluetun[dot]com by setting BORINGPOLL_GLUETUNCOM=on on the latest image.
See the option in the wiki for more information

This is an automated comment setup because @qdm12 is the sole maintainer of this project
which became too popular to monitor closed issues.

[qdm12]

Done in cc5b435! Thanks for the investigation to find the URL 😉
For now, please update the servers using the gluetun update command, and you should obtain IPv6 addresses in there.

[qdm12]

I tested this with custom provider and it works well. No leaks

IPv6 has been supported for a while for other providers, so there shouldn't be leaks 😉
Actually a better way to test is to docker exec -it gluetun ip link set tun0 down && docker exec -it gluetun wget -qO- https://github.com to see if it "successfully" fails, given otherwise routing just takes care of routing packets through the VPN.
Actually number 2, if you don't mind, maybe you could update your servers data, and then test out #3157 (image tag pr-3157 + FIREWALL_IMPLEMENTATION=nftables) to see if there is a leak? That way you can check two things at the same time for me! 😉

[ranile]

@qdm12 I tested it and v6 connectivity isn't present by default. I need to set WIREGUARD_ADDRESSES: 10.2.0.2/32,2a07:b944::2:2/128 environment variable for there to be a v6 route. I also can't get gluetun to connect to protonvpn over v6 with protonvpn provider. Even setting WIREGUARD_ENDPOINT_IP: 2a02:6ea0:d101:2282::10 and reducing the server list down to one server results in:

2026-08-25T20:52:16+08:00 ERROR [vpn] finding a VPN server: target IP address not found: in 1 filtered connections