Closed loscamos closed 7 months ago
loscamos
commented
9 months ago The only way to make it work is to leave the
OPENVPN_CONFIG
empty. I could find the correct way to input a opvn server. I tried
it-mil-ovpn-201 it-mil-ovpn-201.mullvad.net it-mil it_mil it_all
All of them results in the error posted above. From the working log the container seems connected to "it-mil-ovpn-201.mullvad.net" but if specified in the CONFIG file it doesn't work.
pkishino
commented
9 months ago no error can be seen in the logs.. not sure you posted it all.. it_all would be the correct name as per above.. did you check the mullvad folder to see what the other configs are named? I only see it_all and it_mil
loscamos
commented
9 months ago It's unbelievable. I spent 6 hours finding the issue. I wouldn't notice it if it wasn't for your comment... I just checked the mullvad folder created after deploying the container. The container starts with all the other ovpn, besides it_all. I opened some of the others ovpn file (ae_all, al_all) and checked them. I then opened the it_all and compared the server to the one present on the mullvad website. There is an error just in the it_all ovpn file generated.
These is the servers listed in the generated file (the wrong one):
remote it-mil-ovpn-101. relays. mullvad.net 1194 remote it-mil-ovpn-102. relays.mullvad. net 1194 remote it-mil-ovpn-103. relays.mullvad. net 1194 remote it-mil-ovpn-104. relays.mullvad. net 1194,
If you check on mullvad website these are correct:
remote it-mil-ovpn-201. relays. mullvad.net 1194 remote it-mil-ovpn-202. relays. mullvad.net 1194
The others are no longer working.
pkishino
commented
9 months ago so, then it seems mullvad just needs someone to create a PR with updates..
Is there a pinned issue for this?
Is there an existing or similar issue for this?
Is there any comment in the documentation for this?
Is this related to the container/transmission?
Are you using the latest release?
Have you tried using the dev branch latest?
Config used
version: "3.3" services: transmission-openvpn: cap_add:
Current Behavior
I am not able to connect with Mullvad. Tried other providers and everything works.
Expected Behavior
Mullvad to connect
How have you tried to solve the problem?
Updated OMV to latest version Updated Docker Removed the container and all dependencies Tried different docker configurations
Log output
Starting container with revision: 81277fb6f8ae6aeb57f913172d4d45c7af8c0b31
TRANSMISSION_HOME is currently set to: /config/transmission-home
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
Will get configs from https://github.com/haugene/vpn-configs-contrib.git
Repository is already cloned, checking for update
Already up to date.
Already on 'main'
Your branch is up to date with 'origin/main'.
Found configs for MULLVAD in /config/vpn-configs-contrib/openvpn/mullvad, will replace current content in /etc/openvpn/mullvad
Starting OpenVPN using config it_all.ovpn
Modifying /etc/openvpn/mullvad/it_all.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
Modification: Updating status for config failure detection
Setting OpenVPN credentials...
adding route to local network 192.168.188.0/24 via 172.26.0.1 dev eth0
2023-10-09 06:09:48 Note: option tun-ipv6 is ignored because modern operating systems do not need special IPv6 tun handling anymore.
2023-10-09 06:09:48 OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 14 2022
2023-10-09 06:09:48 library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10
2023-10-09 06:09:48 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2023-10-09 06:09:48 TCP/UDP: Preserving recently used remote address: [AF_INET]89.40.182.210:1194
2023-10-09 06:09:48 Socket Buffers: R=[212992->425984] S=[212992->425984]
2023-10-09 06:09:48 UDP link local: (not bound)
2023-10-09 06:09:48 UDP link remote: [AF_INET]89.40.182.210:1194
Environment
Anything else?
No response