qdm12 / gluetun-wiki

Home to the Markdown Wiki page for Gluetun
MIT License
269 stars 31 forks source link

Gluetun container unhealthy NordVPN #50

Open spike63995 opened 3 months ago

spike63995 commented 3 months ago

Hi,

I have looked up this issue as best I could but I kept finding unrelated topics. Basically I have unraid and have tried setting up the gluetun container under wireguard for Nord. I followed the instructions of inputting the IP I receive from Nord on my Ubuntu VM into the assigned field. I got my private and shared key from there as well. I believe I have everything set up the way it should be. But if you can see anything in my config that is not properly set up, please let me know. I have attached the logs. Below is the error I'm receiving over and over. I of course tried the website it gives me, but did not solve my problem.

_GluetunVPN_logs(1).txt

2024-03-04T05:17:38-05:00 INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working. 2024-03-04T05:17:38-05:00 INFO [dns] downloading DNS over TLS cryptographic files 2024-03-04T05:17:46-05:00 INFO [healthcheck] program has been unhealthy for 6s: restarting VPN 2024-03-04T05:17:46-05:00 INFO [healthcheck] 👉 See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md 2024-03-04T05:17:46-05:00 INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION 2024-03-04T05:17:46-05:00 INFO [vpn] stopping 2024-03-04T05:17:46-05:00 ERROR [vpn] cannot get version information: Get "https://api.github.com/repos/qdm12/gluetun/commits": context canceled 2024-03-04T05:17:46-05:00 ERROR [ip getter] Get "https://ipinfo.io/": dial tcp: lookup ipinfo.io on 1.1.1.1:53: write udp 172.17.0.9:59207->1.1.1.1:53: write: operation not permitted - retrying in 5s

fijibestwater commented 3 months ago

I've been having the same issue since yesterday using mullvad. I had it running fine in docker for several weeks when out of the blue yesterday it broke. My logs look the exact same as OP's.