Wireguard connection won't work

[solidsnakex37]

My VPN won't go to a healthy status, I haven't made any changes. I'm running it in unraid on the latest tag. Below are what the logs show, not sure what the issue is. It was working flawless until 18 hours ago, it stopped and I haven't been able to get it working again. I've tried turning off the firewall, turning off DOT. Changing the dns over tls provider, no go.

2022-07-10T19:16:02Z INFO [vpn] starting
2022-07-10T19:16:02Z INFO [firewall] allowing VPN connection...
2022-07-10T19:16:03Z INFO [wireguard] Using available kernelspace implementation
2022-07-10T19:16:03Z INFO [wireguard] Connecting to 89.45.90.184:51820
2022-07-10T19:16:03Z INFO [wireguard] Wireguard is up
2022-07-10T19:16:10Z WARN [dns over tls] cannot update files: Get "https://www.internic.net/domain/named.root": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
2022-07-10T19:16:10Z INFO [dns over tls] attempting restart in 10s
2022-07-10T19:16:14Z INFO [healthcheck] program has been unhealthy for 11s: restarting VPN
2022-07-10T19:16:14Z INFO [vpn] stopping
2022-07-10T19:16:14Z INFO [vpn] starting
2022-07-10T19:16:14Z INFO [firewall] allowing VPN connection...
2022-07-10T19:16:14Z INFO [wireguard] Using available kernelspace implementation
2022-07-10T19:16:14Z INFO [wireguard] Connecting to 194.110.112.2:51820
2022-07-10T19:16:14Z INFO [wireguard] Wireguard is up
2022-07-10T19:16:20Z INFO [dns over tls] downloading DNS over TLS cryptographic files
2022-07-10T19:16:30Z INFO [healthcheck] program has been unhealthy for 16s: restarting VPN
2022-07-10T19:16:30Z INFO [vpn] stopping

[qdm12]

So Wireguard is a silent protocol so it won't alert you if the vpn server is down, or your key is bad, or you have 0 internet. It's usually one of these 3 reasons.

Is your subscription over? (happened to me)
Does your Internet on that machine work?
Do you have a firewall blocking outbound connections?

You can also try using an older image tag like qmcgaw/gluetun:v3.29.0 to see if it helps?

[qdm12]

Maybe it's outdated servers picked up at random, try using the same working server hostname set as SERVER_HOSTNAME?

[giovannipollo]

I tried the working one by specifying it with SERVER_HOSTNAME.
I also noticed that the first time after boot it uses the userspace, while the other times it uses the kernelspace. Can this be a problem? Is it possibile to force one or the other?

[qdm12]

I think someone had this issue already, maybe wireguard takes time to load in the kernel 🤔 Do you launch docker and gluetun as soon as the boot completes? Have you tried launching it with a minute of delay?

[qdm12]

Then, if for some reason I need to stop the container and restart it, it does not work. So I need to reboot the server and then if I start the container it works again.

Please create another Github issue with your config and logs

[giovannipollo]

I think someone had this issue already, maybe wireguard takes time to load in the kernel 🤔 Do you launch docker and gluetun as soon as the boot completes? Have you tried launching it with a minute of delay?

I tried everything. Waiting, launching immediately and so on.

Then, if for some reason I need to stop the container and restart it, it does not work. So I need to reboot the server and then if I start the container it works again.

Please create another Github issue with your config and logs

Yes, for sure. In the weekend, that I have more time and I can reboot the server, I will open an issue and post the logs. Thanks for your support!