Bug: Mullvad - Can't Access to Osaka
xrfmkrh opened this issue · comments
Is this urgent?
None
Host OS
Synology
CPU arch
None
VPN service provider
Mullvad
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on 2024-05-02T16:57:20.083Z (commit fb145d6)
What's the problem 🤔
I can access to other cities(Tokyo, New York NY, ...) but I can't access to Osaka only. This has been happening for few months, not just in this version.
Share your logs (at least 10 lines)
2024/05/03 03:45:18 stdout 2024-05-03T03:45:18+09:00 ERROR [ip getter] Get "https://ipinfo.io/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) - retrying in 2m40s
2024/05/03 03:45:17 stdout 2024-05-03T03:45:17+09: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/05/03 03:45:17 stdout 2024-05-03T03:45:17+09:00 INFO [wireguard] Connecting to 45.8.223.240:51820
2024/05/03 03:45:17 stdout 2024-05-03T03:45:17+09:00 INFO [wireguard] Using available kernelspace implementation
2024/05/03 03:45:17 stdout 2024-05-03T03:45:17+09:00 INFO [firewall] allowing VPN connection...
2024/05/03 03:45:17 stdout 2024-05-03T03:45:17+09:00 INFO [vpn] starting
2024/05/03 03:45:17 stdout 2024-05-03T03:45:17+09:00 INFO [vpn] stopping
2024/05/03 03:45:17 stdout 2024-05-03T03:45:17+09:00 INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION
2024/05/03 03:45:17 stdout 2024-05-03T03:45:17+09:00 INFO [healthcheck] 👉 See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
2024/05/03 03:45:17 stdout 2024-05-03T03:45:17+09:00 INFO [healthcheck] program has been unhealthy for 46s: restarting VPN
2024/05/03 03:44:30 stdout 2024-05-03T03:44:30+09: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/05/03 03:44:30 stdout 2024-05-03T03:44:30+09:00 INFO [wireguard] Connecting to 45.8.223.240:51820
2024/05/03 03:44:30 stdout 2024-05-03T03:44:30+09:00 INFO [wireguard] Using available kernelspace implementation
2024/05/03 03:44:29 stdout 2024-05-03T03:44:29+09:00 INFO [firewall] allowing VPN connection...
2024/05/03 03:44:29 stdout 2024-05-03T03:44:29+09:00 INFO [vpn] starting
2024/05/03 03:44:29 stdout 2024-05-03T03:44:29+09:00 INFO [vpn] stopping
Share your configuration
gluetun:
image: qmcgaw/gluetun:latest
network_mode: bridge
cap_add:
- NET_ADMIN
devices:
- /dev/net/tun:/dev/net/tun
volumes:
- /volume1/docker/gluetun:/gluetun
environment:
- VPN_SERVICE_PROVIDER=mullvad
- VPN_TYPE=wireguard
- WIREGUARD_PRIVATE_KEY=
- WIREGUARD_ADDRESSES=
- SERVER_CITIES=Osaka
restart: unless-stopped
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
Please:
- do not ask for updates, be patient
- 👍 the issue to show your support instead of commenting
@qdm12 usually checks issues at least once a week, if this is a new urgent bug,
revert to an older tagged container image
See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md
Update your servers data, the server 45.8.223.240 you are trying to use is no longer valid
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.