Bug: server does not support port forwarding

[Korunos47]

Is this urgent?

Yes

Host OS

Unraid

CPU arch

x86_64

VPN service provider

ProtonVPN

What are you using to run the container

Unraid

What is the version of Gluetun

Running version latest built on 2024-07-31T21:07:07.349Z (commit ceb6ff4)

What's the problem 🤔

Since the latest commit, we're getting the error that the server does not support port forwarding.
I tried the PR-2383 tag which worked perfectly fine.

Share your logs (at least 10 lines)

2024-08-01T08:13:02Z INFO [routing] default route found: interface eth0, gateway 172.21.0.1, assigned IP 172.21.0.2 and family v4
2024-08-01T08:13:02Z INFO [routing] adding route for 0.0.0.0/0
2024-08-01T08:13:02Z INFO [firewall] setting allowed subnets...
2024-08-01T08:13:02Z INFO [routing] default route found: interface eth0, gateway 172.21.0.1, assigned IP 172.21.0.2 and family v4
2024-08-01T08:13:02Z INFO TUN device is not available: open /dev/net/tun: no such file or directory; creating it...
2024-08-01T08:13:02Z INFO [dns] using plaintext DNS at address 1.1.1.1
2024-08-01T08:13:02Z INFO [http server] http server listening on [::]:8000
2024-08-01T08:13:02Z INFO [firewall] allowing VPN connection...
2024-08-01T08:13:02Z INFO [healthcheck] listening on 127.0.0.1:9999
2024-08-01T08:13:02Z INFO [wireguard] Using available kernelspace implementation
2024-08-01T08:13:02Z INFO [wireguard] Connecting to 212.92.104.241:51820
2024-08-01T08:13: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-08-01T08:13:02Z INFO [healthcheck] healthy!
2024-08-01T08:13:02Z INFO [dns] downloading DNS over TLS cryptographic files
2024-08-01T08:13:03Z INFO [dns] downloading hostnames and IP block lists
2024-08-01T08:13:07Z INFO [http server] 200 GET /portforwarded wrote 11B to 127.0.0.1:48758 in 105.718µs
2024-08-01T08:13:08Z INFO [dns] init module 0: validator
2024-08-01T08:13:08Z INFO [dns] init module 1: iterator
2024-08-01T08:13:08Z INFO [dns] start of service (unbound 1.20.0).
2024-08-01T08:13:08Z INFO [dns] generate keytag query _ta-4a5c-4f66-9728. NULL IN
2024-08-01T08:13:08Z INFO [dns] generate keytag query _ta-4a5c-4f66-9728. NULL IN
2024-08-01T08:13:09Z INFO [dns] ready
2024-08-01T08:13:09Z INFO [ip getter] Public IP address is 212.92.104.246 (Netherlands, North Brabant, Roosendaal)
2024-08-01T08:13:09Z INFO [vpn] You are running on the bleeding edge of latest!
2024-08-01T08:13:09Z INFO [port forwarding] starting
2024-08-01T08:13:09Z ERROR [vpn] port forwarding for the first time: server does not support port forwarding

Share your configuration

gluetun:
    image: qmcgaw/gluetun:latest
    container_name: gluetun
    restart: always
    cap_add:
      - NET_ADMIN
    environment:
      - VPN_TYPE=wireguard
      - VPN_SERVICE_PROVIDER=custom
      - VPN_ENDPOINT_IP=212.92.104.241
      - VPN_ENDPOINT_PORT=51820
      - WIREGUARD_PUBLIC_KEY=XXX
      - WIREGUARD_PRIVATE_KEY=XXX
      - WIREGUARD_ADDRESSES=10.2.0.2/32
      - VPN_PORT_FORWARDING=on
      - VPN_PORT_FORWARDING_PROVIDER=protonvpn
    ports:
      - 8090:8090
      - 6881:6881
      - 6881:6881/udp

[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

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

[qdm12]

34e8f5f might resolve it I think. I'm re-opening this just to wait for your feedback to make sure it's solved.

[Korunos47]

It's fixed with the latest commit. Thank you very much

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