Bug: internal healthcheck not detecting failed connection #2395
Comments
|
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
qdm12
changed the title
|
What you can try to further debug this:
By default, you can only access it from within Gluetun (or perhaps a connected container), since gluetun/internal/healthcheck/handler.go Lines 27 to 31 in 8dbe7b8 And in your case, it looks like the healthcheck is "happy" (aka no error), although the connection doesn't seem to work.
No, it's meant to always execute according to periods pre-defined, in the code block there: It's rather not-that-complicated and looking like it should work fine. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
qdm12
changed the title
|
Indeed I get an empty response from healthcheck server. it seems I have a connection... : However port doesn't seem forwarded. Qbt electrocardiogram seems dead, torguard ip check can't see anything, qbt won't connect to new trackers. |
|
I'm deeply sorry for the time you lost, the culprit here is qbittorrent, it seems it just gives up after a few dozens of reconnections. Anyway there's also something wrong about ProtonVPN with all of this, i'll get in contact with them as it seems I'm not the only one to get such unstable connections. |
|
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 |
No worry at all, thank you for clarifying this that fast 💯
Have you tried the (newly added) Wireguard implementation for protonvpn (see the wiki, you just need your wireguard private key)? I tried it and it was working fine (at least for 1-2 hours when I was debugging something). |
|
If you talk about the internal wireguard configuration we tested with Doug and you the other day then yes ^^ that's what I'm using. |
|
For information |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this urgent?
It may be if healthcheck is the culprit...
Host OS
DSM 7.2.1
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-08-03T14:43:22.495Z (commit 1918be6)
What's the problem 🤔
As you may know now, those times ProtonVPN french servers are quite unstable (verified with another system).
Tonight I got some usual servers switches triggered, nothing fancy, but after a while I think the healthcheck just stopped working along with server rotation and today there was no connection anymore on my side of the tunnel.
I'm sorry not to have much information to give besides those logs.
I believe the internal healthcheck should have its own "server", is there a way to access it manually for further investigation? tried serveradress:9999 but did not work, same for 127.0.0.1:9999 on the local system.
Also, is there a command to trigger an internal healthcheck ?
Thanks
Share your logs (at least 10 lines)
Share your configuration
The text was updated successfully, but these errors were encountered: