-
-
Notifications
You must be signed in to change notification settings - Fork 326
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: failure to renew port forwarding shuts down the container #2274
Comments
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
This comment was marked as off-topic.
This comment was marked as off-topic.
I also saw that yesterday actually, it's due to nf_tables misbehaving (I reported the bug to the netfilter project) which is now the default backend for iptables since the upgrade to Alpine 3.19. I have a local fix which prefers using the legacy version of iptables (not using nf_tables). I'll push it later today, in the meantime use :v3.38 |
Actually the fix was pushed yesterday in commit ce642a6 so just re-pull the latest image and it should be fixed. I'll close this assuming this is resolved. |
Closed issues are NOT monitored, so commenting here is likely to be not seen. This is an automated comment setup because @qdm12 is the sole maintainer of this project |
Is this urgent?
Yes
Host OS
endeavouros
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-05-09T14:36:40.530Z (commit ce642a6)
What's the problem 🤔
Marked urgent, because container shuts itself down.
Occasionally with proton vpn port forwarding setup (on either wireguard or openvpn), I see that container shut down after the following error:
This issue is intermittent, and usually appears within 5 minutes of starting container. All the other services connected via gluetun are rendered inaccessible.
My understanding is that port forwarding is being renewed on proton server every 60 seconds, and it that fails gluetun double-frees the iptables rule for the port being forwarded.
Note: I've been seeing other failures to connect to proton, which usually look like this:
and repeating. It might be related to me pulling a lot of data in short amount of time, and proton throttling me (even though running wireguard config on host - without port forwarding - seems to be ok). I'm not sure what to do with it yet, but I can try and provide more info if needed.
Share your logs (at least 10 lines)
Share your configuration
The text was updated successfully, but these errors were encountered: