-
-
Notifications
You must be signed in to change notification settings - Fork 329
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: ProtonVPN Wireguard port forwarding stop working - unable to grab open port #1891
Comments
So I did experience this issue with wireguard aswell and have not been able to figure out why, for now the solution I found is to switch back to OpenVPN and that has worked flawlessly with QBittorrent + A port mapping script to automatically update it. |
You mean every time on the same server you'll get the error:
Eventhough it works to get the external address:
Correct? If that is the case, this is kind of strange, since both the 'external address' and the 'add port mapping' use the same underlying protocol with the vpn gateway to communicate. It might be worth asking protonvpn's support why this fails? 🤔 Or try with |
EDIT: I think this actually has to do with the ipinfo TOO MANY REQUESTS issue currently happening as re-reading this log, it's a different error than the one I reported So this is currently happening with my gluetun container again so here is the full log:
|
I had just had the exact same issue with protonvpn and it turns out the vpn server I connected to was down. I just switched to another server that was up according to protonvpn, but I got the same result. When I tried again a different server, but this time in another country, the issue was solved somehow. |
@CplPwnies the last log you sent has a few interesting things, although it seems unrelated to the original issue. What you see are consequences of the VPN tunnel being unhealthy (connecitivity not working). In more details:
|
@qdm12 - Yes, the log I posted yesterday seemed to be a ProtonVPN issue. I switched VPN servers and this fixed that issue. To answer your other question though about the original error and log - yes, the port forwarding stops working even though it does grab the external IP correctly. It's super strange. |
Okay, Apologies for the radio silence on this - I thought I might have corrected the issue due to a misconfiguration on one of my containerized applications still seeking out it's own NAT-PMP and causing me to grab more than one port-forward, but I have since fixed that and everything seemed stable... until last night when I lost my port-forward again. Here is the log from the past ~5 days:
|
I am closing this issue because
|
Is this urgent?
No
Host OS
Debian Bullseye
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 2023-09-28T14:05:11.407Z (commit d4df872)
What's the problem 🤔
I just recently switched to ProtonVPN and also gluetun for the NAT-PMP port forwarding support. I have been able to successfully get port forwarding working with the custom wireguard provider, however I've noticed after a period of time, the gluetun container stops being able to get a port from NAT-PMP and the container gets stuck in a restart loop.
The only way I've found to fix this is to generate a new WG config from Proton's website and updating my compose file (essentially switching servers)
Share your logs (at least 10 lines)
Share your configuration
The text was updated successfully, but these errors were encountered: