Closed proudhon closed 1 year ago
Having the exact same issue with mullvad.
Have you tried image qmcgaw/gluetun:v3.35.0
?
Have you tried updating servers data?
@AliceGrey Just ran mine with Mullvad + Wireguard without any problem, maybe one particular server Ip address is outdated, you may want to update your servers data as well.
Running the manual update results in:
2023-07-25T23:35:22Z ERROR updating server information: getting servers: not enough servers found: 188 and expected at least 292
Also if understand the logs correctly:
gluetun-gluetun-1 | 2023-07-26T01:48:17+02:00 INFO [vpn] starting gluetun-gluetun-1 | 2023-07-26T01:48:17+02:00 INFO [firewall] allowing VPN connection... gluetun-gluetun-1 | 2023-07-26T01:48:17+02:00 INFO [wireguard] Using available kernelspace implementation gluetun-gluetun-1 | 2023-07-26T01:48:17+02:00 INFO [wireguard] Connecting to 185.102.217.196:51820 gluetun-gluetun-1 | 2023-07-26T01:48:17+02:00 INFO [wireguard] Wireguard is up
It looks like wireguard successfully connects to the surfshark server (that ip is updated and it is the one shown by surfshark's webui control panel for manual configuration of vpn clients).
i'm running some basic network tests on the container and it looks like it can't resolve hostnames and doesn't have outbound connectivity:
$ docker container exec -it gluetun-gluetun-1 sh
/ # ping archlinux.org
ping: bad address 'archlinux.org'
$ docker container exec -it gluetun-gluetun-1 sh
/ # ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
^C
--- 1.1.1.1 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
@proudhon
Running the manual update results
you can use -minratio 0.5
to change the ratio (0 to 1) to work around the minimum number of servers required to pass the update (by default it's 0.8). It was not really documented, I added a warning in case not enough servers are found in dc8fc5f81f6426bdc1dddbdd5f822f201a623aa3
I also updated Surfshark servers data in b787e12e253e2cc626232796b33c5a15a8d936a3 so you can just pull the latest image for this time 😉
It looks like wireguard successfully connects to the surfshark server
Not necessarily, as the log explains it better now:
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.
It likely is not connecting at all in fact.
After updating my servers data locally, the ip address you used 185.102.217.196
is no longer there, so it's most likely a no longer working ip address (despite being on their UI, it might also be outdated over there 🤔)
Anyway, I'll close this issue assuming it's back to working state now, please open a new issue if the problem still persists, thanks!
Is this urgent?
Yes
Host OS
Debian Bookworm
CPU arch
x86_64
VPN service provider
Surfshark
What are you using to run the container
docker-compose
What is the version of Gluetun
version latest built on 2023-07-22T16:07:05.641Z (commit eecfb39)
What's the problem 🤔
The rootless container will constantly restart, either with openvpn or wireguard. (this also occurs by running the containers with a privileged user). I'm starting the rootless container on a Debian bookworm vm on a proxmox server. The vm itself has no firewall, and proxmox's firewall shouldn't block any outbound connection. Other containers are running fine on the same machine. I can successfully connect to the hosts:ports that appear in the logs via telnet. I know it's probably me missing something but I tried everything in my power/knowledge.
Share your logs
Share your configuration