mullvad has many hosts wrong, resolve errors

chadmiller commented 1 year ago

Is there a pinned issue for this?

[X] I have read the pinned issues

Is there an existing or similar issue for this?

[X] I have searched the existing issues

Is there any comment in the documentation for this?

[X] I have read the documentation, especially the FAQ and Troubleshooting parts

Is this related to the container/transmission?

[X] I have checked the container repo for issues

Are you using the latest release?

[X] I am using the latest release

Have you tried using the dev branch latest?

[X] I have tried using dev branch

Config used

with config "us-atl" or "default", I get many resolution errors.

Current Behavior

from my log file,

 nl-ams-011.mullvad.net:1195 (Name or service not known)
 nl-ams-018.mullvad.net:1195 (Name or service not known)
 us-atl-001.mullvad.net:1302 (Name or service not known)
 us-atl-002.mullvad.net:1302 (Name or service not known)
 us-atl-101.mullvad.net:1302 (Name or service not known)
 us-atl-102.mullvad.net:1302 (Name or service not known)
 us-atl-103.mullvad.net:1302 (Name or service not known)
 us-atl-104.mullvad.net:1302 (Name or service not known)
 us-atl-105.mullvad.net:1302 (Name or service not known)

Expected Behavior

hosts are valid

How have you tried to solve the problem?

Noticed the name-atl-104.mullvad.net

is not like the pattern us-atl-ovpn-104.relays.mullvad.net

https://mullvad.net/en/servers/

Log output

 Starting container with revision: a95f586492b2b7e8ff2cc8ac7f91bc43c0cccc40
 Creating TUN device /dev/net/tun
 Using OpenVPN provider: MULLVAD
 Running with VPN_CONFIG_SOURCE auto
 No bundled config script found for MULLVAD. Defaulting to external config
 Downloading configs from https://github.com/haugene/vpn-configs-contrib/archive/main.zip into /tmp/tmp.YUTJCTUMtP
 Extracting configs to /tmp/tmp.lPwDv7iZGV
 Found configs for MULLVAD in /tmp/tmp.lPwDv7iZGV/vpn-configs-contrib-main/openvpn/mullvad, will replace current content in /etc/openvpn/mullvad
 Cleanup: deleting /tmp/tmp.YUTJCTUMtP and /tmp/tmp.lPwDv7iZGV
 Starting OpenVPN using config default.ovpn
 Modifying /etc/openvpn/mullvad/default.ovpn for best behaviour in this container
 Modification: Point auth-user-pass option to the username/password file
 Modification: Change ca certificate path
 Modification: Change ping options
 Modification: Update/set resolv-retry to 15 seconds
 Modification: Change tls-crypt keyfile path
 Modification: Set output verbosity to 3
 Modification: Remap SIGUSR1 signal to SIGTERM, avoid OpenVPN restart loop
 Setting OpenVPN credentials...
 [23:49:55] [INF] [54] Jellyfin.Networking.Manager.NetworkManager: Defined LAN addresses : [10.41.15.0/24]
 [23:49:55] [INF] [54] Jellyfin.Networking.Manager.NetworkManager: Defined LAN exclusions : []
 [23:49:55] [INF] [54] Jellyfin.Networking.Manager.NetworkManager: Using LAN addresses: [10.41.15.0/24]
 adding route to local network 10.41.15.0/24 via 172.29.0.1 dev eth0
 Sat Oct 15 19:49:55 2022 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar 22 2022
 Sat Oct 15 19:49:55 2022 library versions: OpenSSL 1.1.1f  31 Mar 2020, LZO 2.10
 Sat Oct 15 19:49:55 2022 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
 Sat Oct 15 19:49:55 2022 RESOLVE: Cannot resolve host address: nl-ams-011.mullvad.net:1195 (Name or service not known)

Environment

- OS: ubuntu
- Docker:

Anything else?

No response

Choff3 commented 1 year ago

I opened a pull request for this issue. https://github.com/haugene/vpn-configs-contrib/pull/151

Choff3 commented 1 year ago

Turns out I was still missing the relay part from the domain name so https://github.com/haugene/vpn-configs-contrib/pull/151 actually did not solve this issue. Will fix and test tomorrow.

Choff3 commented 1 year ago

@pkishino New PR #153 confirmed working.

haugene / vpn-configs-contrib