I have recently been having a lot of issues maintaining a connection with my proton vpn in gluetun. it keeps dropping and reconnecting due to failing periodic small health check. My internet connection is solid without connection issues, running a symmetrical 1gbit and the router (gl.inet brume 2) doesn’t register any dropouts in connection.
i have tried following the suggested troubleshooting in the docs, updating the vpn server list etc., but none of the suggestions seem to fix this issue. it has been going on for several months now. if i use mullvad it works perfectly without connection issues, but this is destroying my seed ratio due to no port forwarding.
It worked without issues for about 1.5year without me changing anything in the compose file, about 6 months ago I started noticing health issues with the container. My torrent stack has been untouched since I set it up 2 years ago.
There doesn’t seem to be a clear pattern in failures, sometimes its 20min, sometimes its 8 hours between failures.
Has your gluetun image been kept up-to-date, btw? Changes to compose file or not, there were IIRC two breaking changes in gluetun connectivity with Proton due to changes in the Proton CLI, the two of them were recent enough, I think in v3.38 and v3.40.
It is updated automatically with watchtower, but I have manually pulled the latest a few times, most recently about two months ago.
Edit: weirdly enough, despite me pulling the latest image just now, which was released two days ago, the log still says I’m running 4 commits behind when I start the container 🤔
Don’t know if proton does offer it, but try to run the raw openvpn (or what the format of proton uses) config in gluetun.
Maybe theres an issue with the native integration.
If it runs fine, I’d say it’s a bug
If it runs just as bad, theres a system issue.
I ran gluetun + proton for 4-5 years. v3.41 broke the integration completely and I could never get it working. Tried both wireguard and ovpn setups.
My best advice is pin to the 3.40 release or change providers. The maintainer hasn’t address the specific problem with proton in over a year. There was some discussion recently about improvements to the healthcheck endpoint, so he is working on the project. But it’s slow going and proton is the only provider I know about that is having consistent issues
3.40 still seems to have this issue, it doesn’t change anything in stability unfortunately.