Bug: Proton VPN Port Forwarding Timeout

[gravelfreeman]

What is the version of Gluetun

Running version v3.39.0 built on 2024-08-09T08:07:23.827Z (commit 09c47c7)

Share your logs (at least 10 lines)

2024-12-12T02:35:02Z INFO [port forwarding] starting
2024-12-12T02:37:10Z ERROR [vpn] port forwarding for the first time: getting external IPv4 address: executing remote procedure call: connection timeout: failed attempts: read udp 172.16.*.*:*****->10.2.*.*:****: i/o timeout (tries 1, 2, 3, 4, 5, 6, 7, 8, 9)
2024-12-12T02:38:10Z INFO [healthcheck] healthy!

Share your configuration

          VPN_TYPE: wireguard
          VPN_SERVICE_PROVIDER: custom
          VPN_PORT_FORWARDING: on
          VPN_PORT_FORWARDING_PROVIDER: protonvpn
          WIREGUARD_ENDPOINT_IP: ${WIREGUARD_ENDPOINT_IP}
          WIREGUARD_ENDPOINT_PORT: ${WIREGUARD_ENDPOINT_PORT}
          WIREGUARD_PUBLIC_KEY: ${WIREGUARD_PUBLIC_KEY}
          WIREGUARD_PRIVATE_KEY: ${WIREGUARD_PRIVATE_KEY}
          WIREGUARD_ADDRESSES: 10.2.*.*/32
          FIREWALL_INPUT_PORTS: ${FIREWALL_INPUT_PORTS}
          FIREWALL_OUTBOUND_SUBNETS: 10.0.0.0/8

[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

[TungstenIodide]

I hit the same issue with version v3.39.1 running with Podman on Fedora CoreOS.

[gravelfreeman]

The issue was

          FIREWALL_OUTBOUND_SUBNETS: 10.0.0.0/8

Which was interfering with the DNS server of Proton which is on 10.2.x.x.

Replaced my config with:

          FIREWALL_OUTBOUND_SUBNETS: 10.0.0.0/16

Issue is gone and port forwarding is working as intended!

[github-actions]

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

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