-
-
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: Forwarded port closed and not reopened in firewall during vpn restart due to unhealthy healthcheck #1801
Comments
Same issue here using proton vpn, wireguard and port forwarding. |
I never managed to get a stable connection with PIA through gluetun. I was having to restart all of my containers multiple times a day trying to get a forwarded port. |
Same problem here with Proton and OpenVPN 2.6. VPN is stable for hours or maybe a couple of days max. Using the REST API to restart the VPN doesn't solve the problem and have to restart the gluetun container. |
See #1749 (comment) and please report on #1749 thanks! |
Fixed in 7120141 (latest image and future release v3.36.0) |
This may still be an issue. I put details in the new issue at the bottom, sorry. |
@akutruff what version are you running?? It's written at the top of your logs. Are you sure you pulled the latest image 🤔 |
For these issues I am running the docker image for pr-1874 and have been pulling periodically. Docker image:
Please let me know if there's a different image to try. From our previous discussions I assumed I should stay on this version. |
FYI, I increased the health check intervals and I have had stable connection and stable port forwarding for almost 24 hours now. I am using the latest image tag. If I return to the default intervals, health checks will fail and the port forwarding will be lost. Note:
|
Is this urgent?
No not any more
Host OS
Debian 12 Bookworm
CPU arch
x86_64
VPN service provider
Private Internet Access
What are you using to run the container
Portainer
What is the version of Gluetun
2023-08-11T11:08:54.752Z (commit e556871)
What's the problem 🤔
When the openvpn connection to private internet access is restarted due to an unhealthy heatlhcheck, the VPN_PORT_FORWARDING_STATUS_FILE is deleted and the forwarded port is closed on the firewall but when the vpn reconnects the port isn't reopened on the firewall and the VPN_PORT_FORWARDING_STATUS_FILE isn't rewritten.
This results in my torrent client just stopping working with no notification which is far from ideal.
This is essentially the same bug as #1749 but happening on openvpn as opposed to wireguard
Share your logs
Share your configuration
The text was updated successfully, but these errors were encountered: