M-archand
commented
8 months ago I don't have any additional information to add, but I just updated to the latest release and I am now experiencing this same issue as well with ProtonVPN as my provider.
Closed pehweihang closed 6 months ago
M-archand
commented
8 months ago I don't have any additional information to add, but I just updated to the latest release and I am now experiencing this same issue as well with ProtonVPN as my provider.
qdm12
commented
8 months ago @pehweihang Have you tried updating servers and checking each possible problem/solution given in the healthcheck page?
@M-archand
I just updated to the latest release
What if you use an older release such as :v3.37, does it work? If it doesn't work either, then it's a server or config issue, try updating servers or change server filters
pehweihang
commented
8 months ago I've tried updating the servers and using other tags (:v3.37, :v3.36).
Looking at the healthcheck page, I don't think its any of the problems listed as I've tried multiple wireguard server configs, only ProtonVPN has this issue (Mullvad works fine).
crispybegs
commented
8 months ago i'm having a similar issue with mullvad, since a gluetun update that ran last night. In portainer, Gluetun seems to start up ok but then after a short while the port mappings disappear and the logs have a bunch of stuff i've never seen before:
2024-03-19T21:32:02Z INFO [routing] default route found: interface eth0, gateway 172.27.0.1, assigned IP 172.27.0.2 and family v4
2024-03-19T21:32:02Z INFO [routing] adding route for 0.0.0.0/0
2024-03-19T21:32:02Z INFO [firewall] setting allowed subnets...
2024-03-19T21:32:02Z INFO [routing] default route found: interface eth0, gateway 172.27.0.1, assigned IP 172.27.0.2 and family v4
2024-03-19T21:32:02Z INFO [dns] using plaintext DNS at address 1.1.1.1
2024-03-19T21:32:02Z INFO [http server] http server listening on [::]:8000
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x78e831]
goroutine 117 [running]:
github.com/qdm12/gluetun/internal/storage.filterServer({{0xc002b5bad0, 0x9}, {0xc002b5baa0, 0x7}, {0x0, 0x0}, {0xc002b5ba98, 0x6}, {0xc002b5baa7, 0x9}, ...}, ...)
github.com/qdm12/gluetun/internal/storage/filter.go:77 +0x1b1
github.com/qdm12/gluetun/internal/storage.(*Storage).FilterServers(_, {_, _}, {{0xc00002a021, 0x9}, {{0x0, 0xffff00000000}, 0xc0000a4000}, {0xc0002dc080, 0x1, ...}, ...})
github.com/qdm12/gluetun/internal/storage/filter.go:33 +0x2fb
github.com/qdm12/gluetun/internal/provider/utils.GetConnection({_, _}, {_, _}, {{0xc00002a021, 0x9}, {{0x0, 0xffff00000000}, 0xc0000a4000}, {0xc0002dc080, ...}, ...}, ...)
github.com/qdm12/gluetun/internal/provider/utils/connection.go:39 +0xad
github.com/qdm12/gluetun/internal/provider/mullvad.(*Provider).GetConnection(_, {{0xc00002a021, 0x9}, {{0x0, 0xffff00000000}, 0xc0000a4000}, {0xc0002dc080, 0x1, 0x1}, {0x0, ...}, ...}, ...)
github.com/qdm12/gluetun/internal/provider/mullvad/connection.go:12 +0x105
github.com/qdm12/gluetun/internal/vpn.setupWireguard({_, _}, {_, _}, {_, _}, {_, _}, {{0xc00002a021, 0x9}, ...}, ...)
github.com/qdm12/gluetun/internal/vpn/wireguard.go:20 +0xbe
github.com/qdm12/gluetun/internal/vpn.(*Loop).Run(0xc0002389a0, {0x109d840, 0xc000100a50}, 0xc000176ba0?)
github.com/qdm12/gluetun/internal/vpn/run.go:40 +0x4f5
created by main._main in goroutine 50
./main.go:427 +0x385a
zpz5HAU-tgc3fgw2xwr
commented
8 months ago Having a similar issue. Everything works again when I use the v3.37 tag.
M-archand
commented
8 months ago @M-archand
What if you use an older release such as
:v3.37, does it work? If it doesn't work either, then it's a server or config issue, try updating servers or change server filters
Older version tags did not seem to work for me. I decided to recreate my wireguard certificate through protonvpn and everything is working again now on the latest version for some reason. Strange since my wireguard connection worked before updating my container, but no complaints from me 😁
pflavio
commented
8 months ago I have the exact same issue although with my own private WireGuard VPN (not a commercial provider). Before the update it was golden.
qdm12
commented
8 months ago Update of the 18th march broke the latest image, pull the latest image again to get the fix from the 19th march. Marking a few of the last comments as hidden since it's off topic.
qdm12
commented
8 months ago @pehweihang please try re-generating a wireguard config file on protonvpn website? 🤔 @M-archand is suggesting this solved it I think.
Otherwise, try with a native Wireguard client (i.e. windows or android app) and a protonvpn config file to check it works fine for a few minutes. This looks to me like a protonvpn server problem, especially since it manages to connect and do a few exchanges successfully, before dying and not being able to reconnect.
pflavio
commented
8 months ago Update of the 18th march broke the latest image, pull the latest image again to get the fix from the 19th march. Marking a few of the last comments as hidden since it's off topic.
Hi so I re-installed the image with the :latest tag again, but now I'm getting the "classic" error:
2024-03-20T16:01:06+01:00 ERROR [ip getter] Get "https://ipinfo.io/": dial tcp: lookup ipinfo.io on 10.8.2.2:53: read udp 10.8.0.2:46161->10.8.2.2:53: i/o timeout - retrying in 10s
2024-03-20T16:01:13+01:00 WARN [dns] cannot update files: Get "https://www.internic.net/domain/named.root": dial tcp: lookup www.internic.net on 10.8.2.2:53: read udp 10.8.0.2:40607->10.8.2.2:53: i/o timeoutI did not make any changes to the container or any settings besides setting the tag and re-deploying it. Any pointers?
pehweihang
commented
8 months ago It seems that it is indeed a ProtonVPN server issue. When using I tried using another country's server config and it works fine, weird that all of my country's servers do not work though.
@qdm12 I think its ok to close this issue now. Thank you for your work on this awesome piece of software!
smolpaw
commented
8 months ago Using ProtonVPN here and the latest works with openvpn.
qdm12
commented
7 months ago When using I tried using another country's server config and it works fine, weird that all of my country's servers do not work though.
Even after a servers data update? Maybe some of them changed IP addresses, that would explain this misbehavior.
qdm12
commented
6 months ago Ok this looks more or less resolved from the original author, as well as other protonvpn users, so closing this. Feel free to also refer to #2154 on possible other reasons you might have an unstable connection.
github-actions[bot]
commented
6 months ago Closed issues are NOT monitored, so commenting here is likely to be not seen. If you think this is still unresolved and have more information to bring, please create another issue.
This is an automated comment setup because @qdm12 is the sole maintainer of this project which became too popular to monitor issues closed.
Is this urgent?
Yes
Host OS
Ubuntu
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-03-07T12:32:25.391Z (commit 3254fc8)
What's the problem 🤔
When using ProtonVPN with Wireguard, it works for a few minutes before it becomes unhealthy and will not recover. The issue persists even after changing the ProtonVPN servers multiple times and also using OpenVPN. I've also tried using the provider Mullvad and there's no issue.
Share your logs (at least 10 lines)
Share your configuration