Bug: Not receiving forwarded port number

jpcapone commented 2 weeks ago

Is this urgent?

None

Host OS

Docker

CPU arch

None

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-08-23T13:50:02.262Z (commit ff7cadb)

What's the problem 🤔

Not receiving forwarded port number - using custom type but the provider is ProtonVPN

Share your logs (at least 10 lines)

2024-08-23T22:36:55Z 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-23T22:36:55Z INFO [healthcheck] healthy!
2024-08-23T22:36:55Z INFO [dns] downloading hostnames and IP block lists
2024-08-23T22:36:55Z INFO [dns] DNS server listening on [::]:53
2024-08-23T22:36:56Z INFO [dns] ready
2024-08-23T22:36:56Z INFO [ip getter] Public IP address is 89.187.180.34 (United States, Illinois, Chicago)
2024-08-23T22:36:56Z INFO [vpn] You are running on the bleeding edge of latest!
2024-08-23T22:36:56Z INFO [port forwarding] starting
2024-08-23T22:36:56Z ERROR [vpn] starting port forwarding service: port forwarding for the first time: getting external IPv4 address: executing remote procedure call: gateway IP is unspecified

Share your configuration

services:
  gluetun:
    image: qmcgaw/gluetun
    cap_add:
      - NET_ADMIN
    environment:
      - VPN_SERVICE_PROVIDER=custom
      - VPN_TYPE=wireguard
      - VPN_ENDPOINT_IP=XXXXXXXXX
      - VPN_ENDPOINT_PORT=51820
      - WIREGUARD_PUBLIC_KEY=XXXXXXXX
      - WIREGUARD_PRIVATE_KEY=sssssssssssssssss
      - WIREGUARD_ADDRESSES=10.2.0.2/32
      - VPN_PORT_FORWARDING=on
      - VPN_PORT_FORWARDING_PROVIDER=protonvpn
      - SHADOWSOCKS=on
      - SHADOWSOCKS_PASSWORD=sssssssssssssssssssss
      - HTTP_CONTROL_SERVER_ADDRESS=:8000

github-actions[bot] commented 2 weeks ago

@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
:+1: 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

CherubUltima commented 2 weeks ago

I got the same error, until this is fixed I reverted back to v3.38.0, port forwarding working there

DARTE5 commented 2 weeks ago

I got the same error. I think they might have accidentally pushed to latest. It seems like 3.39 is supposed to be the latest release. I switched to qmcgaw/gluetun:v3.39 and it’s working again.

jpcapone commented 2 weeks ago

reverting did the trick. Thanks for the assist! I'll be more than happy to help troubleshooting just let me know.

qdm12 commented 2 weeks ago

This is due to the upgrade to netlink 2 days ago 540acc915d56ba1c0a2c51edd2f0f1399a9e861a thanks for the fast feedback guys 💪 💯

Working on a fix...

qdm12 commented 2 weeks ago

Fixed in 01fa9934bce4fe49e8fe7c97ecfd74eaf2c9d807 ! Thanks again for taking the time to report this and comment 😉 !

github-actions[bot] commented 2 weeks ago

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 / gluetun