Bug: Wireguard not working after v3.35.0 #1819
Comments
|
I am experiencing the same problems. I just can't get any connection working. |
|
Also having thing this issue. I rolled back to 3.34.1 and it's working again but I don't know what's changed since. Tried setting the new-ish variable WIREGUARD_MTU to what my VPN sets but didn't fix it. |
I've downgraded to 3.34.3, worked like a charm. Hopefully a patch is released soon. |
|
@legraml @Egonor @ddevilbissjr what provider are you using? @Egonor @ddevilbissjr is v3.35.0 working? is the latest image working? |
qdm12
changed the title
|
EDIT: v3.35 does work TorGuard on Unraid from Community Applications/latest from docker does not work. Setup with Trash guide and port forwarding, only thing not setup that shows up in debug logs is Wireguard Pre-shared Key: [not-set]. There doesn't seem to be much in the debug logs but if you need me to do something let me know |
qdm12
changed the title
|
The latest image still works for me with Wireguard + Mullvad. @Egonor what provider are you using?? The changes between v3.35.0 and the latest image are listed here: v3.35.0...master For example, to build the image corresponding to commit fbe252a docker build -t qmcgaw/gluetun:test https://github.com/qdm12/gluetun#fbe252a9b60847bdf6ba7309dce7a946c19f9e33And then you can run |
|
@Egonor Little weekend ping 😉 This is a blocking issue for the next (long overdued) v3.36 release 🔮 |
|
@qdm12 My provider is TorGuard I'm running it through Unraid so I setup docker desktop but every version I try is having health check restarts due to "DNS over TLS cannot update files" or "unhealthy: dialing: dial tcp4: lookup cloudflare.com: i/o timeout" so I can't find a good config to even get a baseline to progress from. Even docker pull qmcgaw/gluetun:v3.35 I tried using minimum wireguard values from the wiki and grabbing the whole docker config from unraid but neither work. |
@qdm12 Sorry for the wait, I've been busy moving between moving homes and reconfigurating my server with new HDDs for ZFS. But I haven't changed any settings from previous versions, any newer version v3.35 or newer results in the same error. I'm using ProtonVPN. |
It's not "due to", it's the VPN connection not working causing these 😉
You previously mentioned @ddevilbissjr no worry for the delay 😉 So it still works with v3.34.3, but not with v3.35.0 or the latest image (make sure you pull it) correct? Can you try setting |
|
v3.35 works for me on UNRAID. I can only pull tagged builds from the dockerhub into Unraid. So to debug a specific build from Git I download Docker for Desktop on a Windows 10 machine but I can't get ANY build working in this environment. I don't know why other than this bug from the wiki or some networking thing I misconfigured or don't know about in Docker/Windows. I normally only run from Unraid. All that to say I can't pinpoint a specific merge without other troubleshooting. I tried some of the more recent than v3.35 PR tags on Unraid and they did not work but I don't know what they correspond to. |
|
also having a similar problem, wireguard custom config fails silently, gives a timeout when trying to reach internic. The same config is working on my router. This is on v3.35.0, amd64 |
|
@Egonor Don't you have ssh access to Unraid and then access to the Have you tried with |
|
Any update? |
Hello @qdm12, Ive reinstalled the docker container on UNRAID and still have the same message, but it can finally connect to the VPN with no problems. There may have been older variables used since the template changed, so that may have prevented the container from connecting properly. Thank you for the continued support. |
|
Ok thanks, I'll close this, if someone encounters this, try updating the Unraid template, or, create another issue 😉 Thanks all! |
Is this urgent?
No
Host OS
Unraid
CPU arch
x86_64
VPN service provider
Custom
What are you using to run the container
docker run
What is the version of Gluetun
2023-08-11T11:08:54.752Z (commit e556871)
What's the problem 🤔
I have an issue where this block of text will keep on repeating:
2023-08-24T00:25:14-07:00 INFO [healthcheck] program has been unhealthy for 36s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md)
2023-08-24T00:25:14-07:00 INFO [vpn] stopping
2023-08-24T00:25:14-07:00 DEBUG [wireguard] closing controller client...
2023-08-24T00:25:14-07:00 DEBUG [wireguard] removing IPv4 rule...
2023-08-24T00:25:14-07:00 DEBUG [wireguard] shutting down link...
2023-08-24T00:25:14-07:00 DEBUG [wireguard] deleting link...
2023-08-24T00:25:14-07:00 INFO [vpn] starting
2023-08-24T00:25:14-07:00 DEBUG [wireguard] Wireguard server public key: pD8KPLHTUnyGvfZxSZn5mgedaIZIr+CV8Ci264WdEWU=
2023-08-24T00:25:14-07:00 DEBUG [wireguard] Wireguard client private key: 2Ia...0s=
2023-08-24T00:25:14-07:00 DEBUG [wireguard] Wireguard pre-shared key: [not set]
2023-08-24T00:25:14-07:00 INFO [firewall] allowing VPN connection...
2023-08-24T00:25:14-07:00 INFO [wireguard] Using available kernelspace implementation
2023-08-24T00:25:14-07:00 INFO [wireguard] Connecting to 146.70.195.34:51820
2023-08-24T00:25:14-07: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.
Logs are not telling me what's preventing the vpn from connecting. My setup has been working with no issues for a long time, randomly no longer works.
Share your logs
Share your configuration
The text was updated successfully, but these errors were encountered: