-
-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: VPN_PORT_FORWARDING_LISTENING_PORT not working #2520
Comments
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
We have no control over the port you get assigned from protonvpn; however the port redirection (for ipv4 only here) should work fine. It's not really logged if it works though, but it's active. You can use |
Doesn't look to good to be honest.
|
The iptables redirection also on IPv4 is not working 😞 |
It is setup correctly for IPv4:
You might be misunderstanding how the VPN server port forwarding works, what's your use case? I guess it's torrenting, and, if so, the forwarded port has to be the one assigned by the vpn provider, not the redirected one, since from an external peer perspective, only the VPN provider assigned port is reachable. You can check it works by following https://github.com/qdm12/gluetun-wiki/blob/main/setup/advanced/vpn-port-forwarding.md#test-it and replace:
|
Is this urgent?
None
Host OS
Ubuntu
CPU arch
x86_64
VPN service provider
ProtonVPN
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on 2024-10-12T14:29:01.263Z (commit 2388e05)
What's the problem 🤔
It's not crashing anymore but also not working... the forwarded port is just a random one, not the one defined in the docker compose yml: - VPN_PORT_FORWARDING_LISTENING_PORT=53411
As you suggested I should reference the old issue.
Thanks in advance.
Share your logs (at least 10 lines)
Share your configuration
The text was updated successfully, but these errors were encountered: