Bug: Renewing Port Restart Gluetun Container using ProtonVPN #2304
Labels
Category: Firewall ⛓️
Category: VPN port forwarding 📥
Priority: 🚨 Urgent
Status: 🟡 Nearly resolved
This might be resolved or is about to be resolved
Status: 🗯️ Waiting for feedback
Comments
|
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
|
Can you run with |
|
Funny enough when i tried to repro the problem, i just wont trigger by itself anymore? then i noticed that to repro the issue, the vpn must be allowed to port forward once then the connection must be unhealthy. So i ran it until it successfully port forwarded and then i disconnected the machine from internet and the bug triggers, anyway here is the log Notes
|
|
Thanks for finding more information on how to reproduce it! 👍 And the last instruction SHOULD delete the rule, since it's present. I suspect 73832d8 solves this, can you try pulling the latest image and check again if it works? Thanks!!! 👍 |
|
So first i tried it on my main pc and it works, but i noticed it used iptables-legacy rather than iptables. My server which has the issue still crashed when disconnected and i attached the log but they are mostly the same as before. I'm curious tho what influence choosing between iptables-legacy or iptables. |
|
On your server, can you try What error do you get? Ideally it would be nice for it to work, I'm not sure why the legacy iptables would not work. The problem is that |
|
Here is the output |
qdm12
added a commit
that referenced
this issue
Jul 28, 2024
- Fix iptables and iptables-nft behavior - Address systems not supporting iptables-legacy, see #2304
|
Welp... Can you try it on both your machines to check if it works fine? This is in the latest image, built today 2024-07-28. |
|
Uhh now it crashed on my pc lol, it seems iptables really hate deleting udp rule and as expected is the same thing in my server |
|
Duplicate of #2334 but let's keep it opened just in case. I'm about to do a v3.39.0 release, and will jump in fixing this (remove iptables rules by line number) right after. |
|
Is this solved using the latest image? Now that other related issues are solved. Thanks! |
|
Sorry for the delay, but i can confirm the latest version doesn't crash anymore when the connection is dropped. I don't need to manually restart my container anymore when the internet does disconnect. |
|
I am using v3.39.0 and am still seeing the same error as @asen23 |
|
@jgramling17 that's expected, it's only fixed in the latest image. I'm fixing 1 or 2 last things before doing a v3.39.1 bugfix release containing that bugfix. |
qdm12
added
the
Status: 🟡 Nearly resolved
Thank you, I ended up figuring it out. Thank you for your patience and contributions to this project ❤️ |
|
v3.39.1 released with that fix, so closing this 😉 ! |
|
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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this urgent?
Yes
Host OS
Fedora Linux 40 (Server Edition)
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-18T18:08:57.405Z (commit 4218dba)
What's the problem 🤔
Whenever the port change it crash the container and restart it causing my other service that depends on gluetun to lose connection. I think it is the same problem with #2274
here is the triggering crash
i also saw other error/warn log but im not sure how related
also some unrelated issue, it sometimes take a long time to connect so i added start_period to prevent timeout when starting docker compose
Share your logs (at least 10 lines)
Share your configuration
The text was updated successfully, but these errors were encountered: