Container exiting after ping timeout, stuck in a loop

[renhardy]

Is there a pinned issue for this?

• I have read the pinned issues and could not find my issue

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

• I have searched the existing issues
• I have searched the existing discussions

Is there any comment in the documentation for this?

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

Is this related to a provider?

• I have checked the provider repo for issues
• My issue is NOT related to a provider

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

Docker run config used

transmission-vpn:
image: haugene/transmission-openvpn:latest
container_name: transmission-vpn
restart: unless-stopped
privileged: true
logging:
driver: syslog
options:
syslog-address: "udp://192.168.XX.XXX:1514"
syslog-format: "rfc5424"
tag: "transmission"
networks:
- t2_proxy
# t2_proxy:
# ipv4_address: 192.168.90.169
# security_opt:
# - no-new-privileges:true
ports:
- "$TRANSMISSION_PORT:9091"
cap_add:
- NET_ADMIN
devices:
- /dev/net/tun
dns:
- 1.1.1.1
- 1.0.0.1
volumes:
- /etc/localtime:/etc/localtime:ro
- $DOCKERDIR/transmission-vpn/data:/data
- $DOCKERDIR/transmission-vpn/config:/config
- $DATADIR/downloads:/downloads
environment:
OPENVPN_PROVIDER: SLICKVPNCORE
OPENVPN_USERNAME: $SLICKVPN_USERNAME
OPENVPN_PASSWORD: $SLICKVPN_PASSWORD
OPENVPN_CONFIG: "Canada-Montreal,Canada-Toronto,United-States-New-York"
#OPENVPN_OPTS: --inactive 3600 --ping 10 --ping-exit 60 --pull-filter ignore ping
LOCAL_NETWORK: "$LOCAL_NETWORK"
PUID: $PUID
PGID: $PGID
TZ: $TZ
UMASK_SET: 2
TRANSMISSION_WEB_UI: "flood-for-transmission"
TRANSMISSION_RPC_AUTHENTICATION_REQUIRED: "false"
TRANSMISSION_RPC_HOST_WHITELIST: "127.0.0.1,$SERVER_IP,192.168.18.1"
TRANSMISSION_RPC_PASSWORD: $TRANSMISSION_RPC_PASSWORD
TRANSMISSION_RPC_USERNAME: $TRANSMISSION_RPC_USERNAME
TRANSMISSION_UMASK: 002
TRANSMISSION_RATIO_LIMIT: 0.01
TRANSMISSION_RATIO_LIMIT_ENABLED: "true"
TRANSMISSION_ALT_SPEED_DOWN: 40000
TRANSMISSION_ALT_SPEED_ENABLED: "false"
TRANSMISSION_ALT_SPEED_UP: 250
TRANSMISSION_SPEED_LIMIT_DOWN: 80000
TRANSMISSION_SPEED_LIMIT_DOWN_ENABLED: "true"
TRANSMISSION_SPEED_LIMIT_UP: 500
TRANSMISSION_SPEED_LIMIT_UP_ENABLED: "true"
TRANSMISSION_INCOMPLETE_DIR: /downloads/torrents/incomplete
TRANSMISSION_INCOMPLETE_DIR_ENABLED: "true"
TRANSMISSION_WATCH_DIR: /downloads/torrents
TRANSMISSION_WATCH_DIR_ENABLED: "true"
TRANSMISSION_DOWNLOAD_DIR: /downloads
CREATE_TUN_DEVICE: "false"

labels:
  - "traefik.enable=true"
  ## HTTP Routers
  - "traefik.http.routers.transmission-vpn-rtr.entrypoints=https"
  - "traefik.http.routers.transmission-vpn-rtr.rule=Host(`trans.$DOMAINNAME`)"
  - "traefik.http.routers.transmission-vpn-rtr.tls=true"
  ## Middlewares
  - "traefik.http.routers.transmission-vpn-rtr.middlewares=chain-authelia@file"
  ## HTTP Services
  - "traefik.http.routers.transmission-vpn-rtr.service=transmission-vpn-svc"
  - "traefik.http.services.transmission-vpn-svc.loadbalancer.server.port=9091"

Current Behavior

I have been struggling with the container restarting in a loop after a ping timeout for a couple of weeks now:

Expected Behavior

The container used to run fine up until october approximately

How have you tried to solve the problem?

I have had this issue before and managed to resolve it by applying the different solutions recommended in the various issues and disccussions relevant to this issue, but this time I cannot make any progress on it.

I have checked the provider and I changed servers to see if it would help, but it does not change the outcome.

I have also forked the vpn-configs-contrib repository to use the latest .ovpn files.

There has been no effects on the issue

Log output

Starting container with revision: 07f5a2b
TRANSMISSION_HOME is currently set to: /config/transmission-home
Using OpenVPN provider: SLICKVPNCORE
Running with VPN_CONFIG_SOURCE auto
No bundled config script found for SLICKVPNCORE. Defaulting to external config
Will get configs from https://github.com/XXXXXXX/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 SLICKVPNCORE in /config/vpn-configs-contrib/openvpn/slickvpncore, will replace current content in /etc/openvpn/slickvpncore
3 servers found in OPENVPN_CONFIG, Canada-Toronto chosen randomly
Starting OpenVPN using config Canada-Toronto.ovpn
Modifying /etc/openvpn/slickvpncore/Canada-Toronto.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.18.0/24 via 192.168.90.1 dev eth0
2024-01-16 14:23:57 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-01-16 14:23:57 OpenVPN 2.5.9 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 29 2023
2024-01-16 14:23:57 library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10
2024-01-16 14:23:57 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2024-01-16 14:23:57 TCP/UDP: Preserving recently used remote address: [AF_INET]172.105.9.120:443
2024-01-16 14:23:57 Socket Buffers: R=[212992->212992] S=[212992->212992]
2024-01-16 14:23:57 UDP link local: (not bound)
2024-01-16 14:23:57 UDP link remote: [AF_INET]172.105.9.120:443
2024-01-16 14:24:57 [UNDEF] Inactivity timeout (--ping-exit), exiting
2024-01-16 14:24:57 SIGTERM[soft,ping-exit] received, process exiting

HW/SW Environment

Running Transmission on a docker 3.6 and Debian10

Anything else?

No response

[jmorata]

same here with latest:

Starting container with revision: 07f5a2b
TRANSMISSION_HOME is currently set to: /config/transmission-home
Creating TUN device /dev/net/tun
Using OpenVPN provider: VYPRVPN
Running with VPN_CONFIG_SOURCE auto
Provider VYPRVPN has a bundled setup script. Defaulting to internal config
Executing setup script for VYPRVPN
Downloading OpenVPN configs into temporary file /tmp/tmp.HkIT4tMljp
Temporarily extracting OpenVPN configs into directory /tmp/tmp.9LNr24Z9pu
Removing /tmp/tmp.9LNr24Z9pu & /tmp/tmp.HkIT4tMljp
Starting OpenVPN using config Spain-256.ovpn
Modifying /etc/openvpn/vyprvpn/Spain-256.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.17.0.1 dev eth0
2024-01-21 15:27:17 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-01-21 15:27:17 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-01-21 15:27:17 OpenVPN 2.5.9 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 29 2023
2024-01-21 15:27:17 library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10
2024-01-21 15:27:17 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2024-01-21 15:27:17 TCP/UDP: Preserving recently used remote address: [AF_INET]128.90.96.30:443
2024-01-21 15:27:17 Socket Buffers: R=[212992->212992] S=[212992->212992]
2024-01-21 15:27:17 UDP link local: (not bound)
2024-01-21 15:27:17 UDP link remote: [AF_INET]128.90.96.30:443
2024-01-21 15:28:17 [UNDEF] Inactivity timeout (--ping-exit), exiting
2024-01-21 15:28:17 SIGTERM[soft,ping-exit] received, process exiting

[jmorata]

fixed with removing OPENVPN_CONFIG set
I was using since last year Spain-256 and now it doesn't runs

[renhardy]

Can you give me more info on how you fixed it please?

[danukefl]

I am also running into the same inactivity timeout with SlickVPN as the provider.

I have, without resolution:

1. updated the healthcheck host to github.com but both github.com and google.com have successful dns lookups and pings when executing within the container
2. Created a new container from the bare default provided config and used my SlickVPN provider
3. Tried latest, dev, master, and v4 branches

[acouvreur]

Same issue here with Hotspot Shield

[danukefl]

In my case, I'm running into the issue on the SlickVPN side specifically with OpenVPN connections. Waiting to hear back from their support.

[renhardy]

@danukefl ,
please tell me if you hear back from SlickVPN support, I have not been able to contact them.

Thanks

[danukefl]

@renhardy I moved over to ProtonVPN which is working running in the latest docker on Debian 12. I'll update if SlickVPN responds but I probably won't be renewing anymore, and this morning their client isn't working either. I've used them for approaching a decade at this point.

[tessierp]

I have the same issue I confirm that removing the OPENVPN_CONFIG reported by @jmorata fixed the issue for me (all versions after 5.2). I regressed to version 5.2 and OPNVPN_CONFIG worked fine, anything after that broke it.

Then I guess something happened with the new release and we are unable to select the particular VPN config we want anymore with the latest version.

[danukefl]

@renhardy Never heard back so I cancelled. Proton is working just fine for me.

[rtrive]

I have the same issue with airvpn. But how can i do this without OPNVPN_CONFIG env?