haugene / docker-transmission-openvpn

Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
GNU General Public License v3.0
4.13k stars 1.21k forks source link

Container will sometimes not start but recomposing will fix it #2377

Closed FaykoB closed 1 year ago

FaykoB commented 2 years ago

Is there a pinned issue for this?

Is there an existing or similar issue/discussion for this?

Is there any comment in the documentation for this?

Is this related to a provider?

Are you using the latest release?

Have you tried using the dev branch latest?

Docker run config used

transmission-openvpn: image: haugene/transmission-openvpn
container_name: mediaRequests_VPN devices:

Current Behavior

my container starts and stops randomly: Starting container with revision: 84941a9ea4663d8b2e1af3db1d50fe4f7fa8736e Creating TUN device /dev/net/tun mknod: /dev/net/tun: File exists 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.crfFG56zzX Extracting configs to /tmp/tmp.pW5w3jK79w Found configs for MULLVAD in /tmp/tmp.pW5w3jK79w/vpn-configs-contrib-main/openvpn/mullvad, will replace current content in /etc/openvpn/mullvad Cleanup: deleting /tmp/tmp.crfFG56zzX and /tmp/tmp.pW5w3jK79w Starting OpenVPN using config us_chi.ovpn Modifying /etc/openvpn/mullvad/us_chi.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... adding route to local network 192.168.0.1/24 via 172.20.0.1 dev eth0 RTNETLINK answers: Invalid argument adding route to local network 192.168.20.1/24 via 172.20.0.1 dev eth0 RTNETLINK answers: Invalid argument adding route to local network 192.168.30.1/24 via 172.20.0.1 dev eth0 RTNETLINK answers: Invalid argument Mon Oct 31 21:24:58 2022 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar 22 2022 Mon Oct 31 21:24:58 2022 library versions: OpenSSL 1.1.1f 31 Mar 2020, LZO 2.10 Mon Oct 31 21:24:58 2022 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Mon Oct 31 21:24:58 2022 RESOLVE: Cannot resolve host address: us-chi-101.mullvad.net:1197 (Name or service not known) Mon Oct 31 21:24:58 2022 RESOLVE: Cannot resolve host address: us-chi-101.mullvad.net:1197 (Name or service not known) Mon Oct 31 21:25:03 2022 RESOLVE: Cannot resolve host address: us-chi-101.mullvad.net:1197 (Name or service not known) Mon Oct 31 21:25:08 2022 RESOLVE: Cannot resolve host address: us-chi-101.mullvad.net:1197 (Name or service not known) Mon Oct 31 21:25:08 2022 Could not determine IPv4/IPv6 protocol Mon Oct 31 21:25:08 2022 SIGTERM[soft,init_instance] received, process exiting

Expected Behavior

to start up normally with no connection issues.

How have you tried to solve the problem?

rebuilding or swapping to glueton/qbt

Log output

Starting container with revision: 84941a9ea4663d8b2e1af3db1d50fe4f7fa8736e Creating TUN device /dev/net/tun mknod: /dev/net/tun: File exists 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.crfFG56zzX Extracting configs to /tmp/tmp.pW5w3jK79w Found configs for MULLVAD in /tmp/tmp.pW5w3jK79w/vpn-configs-contrib-main/openvpn/mullvad, will replace current content in /etc/openvpn/mullvad Cleanup: deleting /tmp/tmp.crfFG56zzX and /tmp/tmp.pW5w3jK79w Starting OpenVPN using config us_chi.ovpn Modifying /etc/openvpn/mullvad/us_chi.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... adding route to local network 192.168.0.1/24 via 172.20.0.1 dev eth0 RTNETLINK answers: Invalid argument adding route to local network 192.168.20.1/24 via 172.20.0.1 dev eth0 RTNETLINK answers: Invalid argument adding route to local network 192.168.30.1/24 via 172.20.0.1 dev eth0 RTNETLINK answers: Invalid argument Mon Oct 31 21:24:58 2022 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar 22 2022 Mon Oct 31 21:24:58 2022 library versions: OpenSSL 1.1.1f 31 Mar 2020, LZO 2.10 Mon Oct 31 21:24:58 2022 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Mon Oct 31 21:24:58 2022 RESOLVE: Cannot resolve host address: us-chi-101.mullvad.net:1197 (Name or service not known) Mon Oct 31 21:24:58 2022 RESOLVE: Cannot resolve host address: us-chi-101.mullvad.net:1197 (Name or service not known) Mon Oct 31 21:25:03 2022 RESOLVE: Cannot resolve host address: us-chi-101.mullvad.net:1197 (Name or service not known) Mon Oct 31 21:25:08 2022 RESOLVE: Cannot resolve host address: us-chi-101.mullvad.net:1197 (Name or service not known) Mon Oct 31 21:25:08 2022 Could not determine IPv4/IPv6 protocol Mon Oct 31 21:25:08 2022 SIGTERM[soft,init_instance] received, process exiting

HW/SW Environment

- OS: Synology DSM
- Docker: 3.9

Anything else?

I'm using traefik as well but doesn't seem like i have issues connecting to these hosts but it just fails. Running compose a few times just resolves it.

pkishino commented 1 year ago

I can see it trying to create invalid routes above and not able to resolve the url.. this is synology related and dsm causes all kinds of strange stuff