Bug: wireguard port forward error with protonvpn

[03184]

Is this urgent?

No

Host OS

Docker

CPU arch

x86_64

VPN service provider

Custom

What are you using to run the container

docker-compose

What is the version of Gluetun

Running version latest built on 2024-12-27T20:18:46.989Z (commit 61b053f)

What's the problem 🤔

Although using wireguard I keep getting an error related to openvpn.

ERROR [vpn] starting port forwarding service: port forwarding for the first time: getting external IPv4 address: executing remote procedure call: reading from udp connection: read udp 10.2.0.2:41931->10.2.0.1:5351: recvfrom: connection refused - make sure you have +pmp at the end of your OpenVPN username

Share your logs (at least 10 lines)

2024-12-31T16:39:02Z INFO [healthcheck] listening on 127.0.0.1:9999

2024-12-31T16:39:02Z INFO [wireguard] Using available kernelspace implementation

2024-12-31T16:39:02Z INFO [wireguard] Connecting to 130.195.250.98:51820

2024-12-31T16:39:02Z INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.

2024-12-31T16:39:02Z INFO [healthcheck] healthy!

2024-12-31T16:39:02Z INFO [dns] downloading hostnames and IP block lists

2024-12-31T16:39:03Z INFO [dns] DNS server listening on [::]:53

2024-12-31T16:39:03Z INFO [dns] ready

2024-12-31T16:39:04Z INFO [ip getter] Public IP address is 130.195.250.122 (Spain, Catalonia, Barcelona - source: ipinfo)

2024-12-31T16:39:04Z INFO [vpn] You are running on the bleeding edge of latest!

2024-12-31T16:39:04Z INFO [port forwarding] starting

2024-12-31T16:39:04Z ERROR [vpn] starting port forwarding service: port forwarding for the first time: getting external IPv4 address: executing remote procedure call: reading from udp connection: read udp 10.2.0.2:41931->10.2.0.1:5351: recvfrom: connection refused - make sure you have +pmp at the end of your OpenVPN username

Share your configuration

name: glueproton
services:
    gluetun:
        stdin_open: true
        tty: true
        cap_add:
            - NET_ADMIN
        devices:
            - /dev/net/tun
        environment:
            - VPN_SERVICE_PROVIDER=custom
            - VPN_TYPE=wireguard
      # OpenVPN:
      #- OPENVPN_USER=
      #- OPENVPN_PASSWORD=
      # Wireguard:
            - WIREGUARD_PUBLIC_KEY=removed # "PublicKey" under [Peer] in WG Config
            - WIREGUARD_PRIVATE_KEY=removed # "PrivateKey" under [Interface] in WG Config - only shown on config creation
            - WIREGUARD_ADDRESSES=10.2.0.2/32 # "Address" under [Interface] in WG Config
            - WIREGUARD_ENDPOINT_IP=130.195.250.98 # "Endpoint" under [Peer] in WG Config
            - WIREGUARD_ENDPOINT_PORT=51820 # should be the default 51820 but can confirm by seeing the port after IP in "Endpoint"
            - VPN_DNS_ADDRESS=10.2.0.1 # "DNS" under [Interface] in WG Config
            - VPN_PORT_FORWARDING=on
            - VPN_PORT_FORWARDING_PROVIDER=protonvpn
        #    - VPN_SERVICE_PROVIDER=protonvpn
        #    - VPN_PORT_FORWARDING=on
        #    - OPENVPN_USER= removed
        #    - OPENVPN_PASSWORD= removed
        #    - SERVER_COUNTRIES=Spain
        image: qmcgaw/gluetun

**** EDIT ****

reverting back to v3.39 fixed issue.

[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

[bazmattaz]

@03184 a lot of us using ProtonVPN are having massive issues with Gluetun V3.4. I've rolled back to qmcgaw/gluetun:v3.39.1 and it works fine. might be worth trying that.

See also this thread:
#2630

[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.