-
-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: ExpressVPN refuses to connect to Montreal #2715
Comments
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
Ok so I think I know where the issue is. The OVPN config created by gluetun for Montreal leads to this
The IP listed here has nothing to do with the hardcoded hostname for Montreal which when resolved shows this as of today
I tested Toronto too and the IP in the OVPN cfg matches one of ones returned by dig. |
Is this urgent?
None
Host OS
Debian Bullseye
CPU arch
x86_64
VPN service provider
ExpressVPN
What are you using to run the container
docker run
What is the version of Gluetun
Running version v3.40.0 built on 2024-12-25T22:01:25.675Z (commit e890c50)
What's the problem 🤔
If I set
SERVER_CITIES
to Montreal it refuses to connect and keeping trying without showing any errors. If I don't set the city, and just set Canada as a country, gluetun will always connect to Toronto (the only other available city). I checked the available servers list and I can ping the hostname for Montreal. I also noticed that the same hostname is specified twice. Montreal only has one entry on the desktop client.I tested the images tagged as latest, v3 and even v3.35 from a year ago and none of them worked.
Changing the log level to debug does not give any useful additional information. Running in privileged mode did not help either.
Share your logs (at least 10 lines)
Share your configuration
The text was updated successfully, but these errors were encountered: