gluetun: Bug: Mullvad M247 server changes - Canada/London/Paris
Hi there, it looks like Mullvad have changed their M247 server list in Canada, London and Paris. Have seen connection issues to Canada and discovered the update on the Mullvad Server page today, so changed over to Sweden which is working fine.
The Mullvad Servers page has the following banners:
M247 - Montreal : ca1,ca3.ca5.ca6.ca8.ca9-wireguard and ca.mtr-0* will be replaced, and will be terminated within 24h. M247 - London : gb1,gb6-wireguard, and gb-lon-20* will be terminated in a couple of days. Aug 4, 2020, 09:33 UTC
M247 Paris - fr1,-wireguardfr2-wireguard,fr3-wireguard,fr-par-1* have been replaced with new servers(fr10-fr14-wireguard and fr-par-20* . Please use the new servers. Aug 3, 2020, 11:03 UTC
Seems really odd that Mullvad don’t have any obvious updates outside their Server page - nothing on their Twitter feed / RSS / blog for example. Wondering if there’s an API of theirs that people can check for this kind of thing, or do they expect their customers to continually scrape their Servers page?
Thanks for your continued efforts on this awesome project!!
-
Is this urgent?
- Yes
- No
-
What VPN service provider are you using?
- PIA
- Mullvad
- Windscribe
- Surfshark
- Cyberghost
-
What’s the version of the program?
Running version latest built on 2020-08-08T16:28:15Z (commit 78323f0) -
What are you using to run the container?
- Docker run
- Docker Compose
- Kubernetes
- Docker stack
- Docker swarm
- Podman
- Other:
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (8 by maintainers)
Since you’re using Mullvad, see #565 since you should now be able to use (or test hehe) Wireguard with it 😉
Oh ok, it’s strange the openvpn config files have a default port changing from one server to another. Anyway, fabulous, I will get to work tonight (got work / sorry for the delay).
On a side note, I’m also planning on having a way to persist IP addresses and regions for vpn providers out of the image and be able to update it locally with the container, so that older docker image tags will still work in the future and I don’t need to update IPs monthly 😄 (have a json file per provider with some funky docker volume manipulation haha)
Perfect, thanks for digging this out.
I’ll use https://api.mullvad.net/public/relays/v1/ should be done today.
I can’t believe I did all these servers manually, what an idiot I was a few months ago 😄