IPVanish config broke

[Neeham]

Is there a pinned issue for this?

• I have read the pinned issues

Is there an existing or similar issue for this?

• I have searched the existing issues

Is there any comment in the documentation for this?

• I have read the documentation, especially the FAQ and Troubleshooting parts

Is this related to the container/transmission?

• I have checked the container repo for issues

Are you using the latest release?

• I am using the latest release

Have you tried using the dev branch latest?

• I have tried using dev branch

Config used

Using the config bundle from IPVanish.

Current Behavior

Transmission start-up is on loop - been working fine since months, randomly stopped starting today.

Expected Behavior

Expected to start Transmission.

How have you tried to solve the problem?

I noticed today the config file were changed on IPVanish website (Wed May 22 19:00:02 2024):
https://configs.ipvanish.com/configs/

Most likely this new config file changes is playing a role.

I did re-pull the latest image and even restart the docker instance.

Log output

Starting container with revision: 07f5a2b9aea5028c9bb75438c1552708e91dde71
TRANSMISSION_HOME is currently set to: /config/transmission-home
WARNING: Deprecated. Found old default transmission-home folder at /data/transmission-home, setting this as TRANSMISSION_HOME. This might break in future versions.
We will fallback to this directory as long as the folder exists. Please consider moving it to /config/transmission-home
Creating TUN device /dev/net/tun
Using OpenVPN provider: IPVANISH
Running with VPN_CONFIG_SOURCE auto
Provider IPVANISH has a bundled setup script. Defaulting to internal config
Executing setup script for IPVANISH
Downloading OpenVPN config bundle configs.zip into temporary file /tmp/tmp.zXtIp7AqkN
Extract OpenVPN config bundle into /etc/openvpn/ipvanish
Starting OpenVPN using config ipvanish-CA-Montreal-yul-c03.ovpn
Modifying /etc/openvpn/ipvanish/ipvanish-CA-Montreal-yul-c03.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.1.0/24 via 172.29.0.1 dev eth0
2024-05-22 22:10:06 WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set.
2024-05-22 22:10:06 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2024-05-22 22:10:06 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
2024-05-22 22:10:06 OpenVPN 2.5.9 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 29 2023
2024-05-22 22:10:06 library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10
2024-05-22 22:10:06 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2024-05-22 22:10:06 TCP/UDP: Preserving recently used remote address: [AF_INET]38.153.100.14:443
2024-05-22 22:10:06 Socket Buffers: R=[819200->819200] S=[819200->819200]
2024-05-22 22:10:06 UDP link local: (not bound)
2024-05-22 22:10:06 UDP link remote: [AF_INET]38.153.100.14:443
2024-05-22 22:11:06 [UNDEF] Inactivity timeout (--ping-exit), exiting
2024-05-22 22:11:06 SIGTERM[soft,ping-exit] received, process exiting
Starting container with revision: 07f5a2b9aea5028c9bb75438c1552708e91dde71

Environment

- OS: linux x86_64 QTS 5.1.5 (20240219)
- Docker: 20.10.27-qnap1

Anything else?

No response

[Neeham]

Started randomly working today :) closing.