-
-
Notifications
You must be signed in to change notification settings - Fork 396
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: [healthcheck] unhealthy: cannot dial: dial tcp4: lookup cloudflare.com: i/o timeout #1164
Comments
i am having the same issues, also with surfshark. ive changed server connections, edited dns, TLS off/on, disabled all blocks and removal of dns cache.. Ive also noticed almost all ove my qbittorrent peer connections enable and quickly disable or timeout from the start. Extending total # of clients allowed per download, as well as altering stop tracker timeout from the default 5 to 10 but its so slow its basically useless. the more gluetin adds the harder it is to prefer |
It's fine if it fails from time to time, as long as it goes back to If it is the VPN connection being unreliable, then it's either:
Well everything added can be disabled so it's just up to you. DNS over TLS can be disabled with |
To anyone still experiencing this issue. TL;DR; Info: I've been fighting with it and trying to find a solution for the past 3 weeks. I suspected it didn't come from gluetun nor the VPN provider. To confirm, I tried running the same setup with another vpn image & another provider, looking at my network inspector I could still see the frequent drops which had the same results in my qBit client (stop/resume). At that point I started wondering if it was an OS or hardware issue, and after a couple of clean OS installs/driver updates, I was still stuck with the same issue. I then suspected something might be failing with Docker itself, seemed a bit far-off but I started searching and stumbled upon this thread. An issue seems to be anchored within the vpnkit and impacts both Mac & Windows user. @qdm12 You might want to keep this in mind for future issues concerning frequent disconnects :) Thanks for your great work on gluetun! |
💯 Awesome! I documented it and linked to your comment in https://github.com/qdm12/gluetun/wiki/Healthcheck#unhealthy (step 4) |
Any fix for this in the works? |
Thank you so much for posting this! I was having the exact same issue and have spent days trying to work this out. The only solution has been to downgrade to v4.5.1 as you said. |
Here is a workaround that resolved the issue for some folks. https://emerle.dev/2022/05/06/the-nasty-gotcha-in-docker/ https://archive.ph/fk6dC (archive of above link) |
@Miexil @qdm12 |
really? downgrading is not an actual fix. |
There is a Dev Build of Docker that appears to resolve this although a different issue arises which causes as this is a dev build your milage may vary moby/vpnkit#587 (comment) |
Is this urgent?
Yes
Host OS
Debian Bullseye
CPU arch
x86_64
VPN service provider
Surfshark
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on 2022-09-14T13:28:28.429Z (commit e5be20d)
What's the problem 🤔
[healthcheck] unhealthy: cannot dial: dial tcp4: lookup cloudflare.com: i/o timeout
After restarting the container, everything is fine again.
It's every day now
Share your logs
Share your configuration
The text was updated successfully, but these errors were encountered: