haugene / docker-transmission-openvpn

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

frequent timeouts #923

Closed spcqike closed 4 years ago

spcqike commented 5 years ago

Describe the problem

The connection times out very often. (every 5-60 minutes) as long as the connection is established, everything works good. but i can't figure out, why there are frequent timeouts.

Add your docker run command

version: "3.6" services: transmission-vpn: container_name: transmission-vpn image: haugene/transmission-openvpn cap_add:

(XXX and PASSWORD/USERNAME is "masked", path-to is shortend)

Logs

Mon Oct 14 13:26:52 2019 Initialization Sequence Completed Mon Oct 14 13:35:52 2019 [vpn-nl.premiumize.me] Inactivity timeout (--ping-restart), restarting Mon Oct 14 13:35:52 2019 SIGUSR1[soft,ping-restart] received, process restarting Mon Oct 14 13:35:52 2019 Restart pause, 5 second(s) Mon Oct 14 13:35:57 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Mon Oct 14 13:35:57 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]185.107.94.249:1194 Mon Oct 14 13:35:57 2019 Socket Buffers: R=[212992->212992] S=[212992->212992] Mon Oct 14 13:35:57 2019 UDP link local: (not bound) Mon Oct 14 13:35:57 2019 UDP link remote: [AF_INET]185.107.94.249:1194 Mon Oct 14 13:35:59 2019 TLS: Initial packet from [AF_INET]185.107.94.249:1194, sid=4c7b1888 c11c8877 Mon Oct 14 13:35:59 2019 VERIFY OK: depth=2, O=Digital Signature Trust Co., CN=DST Root CA X3 Mon Oct 14 13:35:59 2019 VERIFY OK: depth=1, C=US, O=Let's Encrypt, CN=Let's Encrypt Authority X3 Mon Oct 14 13:35:59 2019 VERIFY X509NAME OK: CN=vpn-nl.premiumize.me Mon Oct 14 13:35:59 2019 VERIFY OK: depth=0, CN=vpn-nl.premiumize.me Mon Oct 14 13:36:00 2019 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA Mon Oct 14 13:36:00 2019 [vpn-nl.premiumize.me] Peer Connection Initiated with [AF_INET]185.107.94.249:1194 Mon Oct 14 13:36:01 2019 SENT CONTROL [vpn-nl.premiumize.me]: 'PUSH_REQUEST' (status=1) Mon Oct 14 13:36:01 2019 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 8.8.4.4,dhcp-option DNS 8.8.8.8,block-outside-dns,route-gateway 10.8.0.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.8.0.15 255.255.0.0,peer-id 26,cipher AES-256-GCM' Mon Oct 14 13:36:01 2019 Options error: Unrecognized option or missing or extra parameter(s) in [PUSH-OPTIONS]:4: block-outside-dns (2.4.7) Mon Oct 14 13:36:01 2019 OPTIONS IMPORT: timers and/or timeouts modified Mon Oct 14 13:36:01 2019 OPTIONS IMPORT: --ifconfig/up options modified Mon Oct 14 13:36:01 2019 OPTIONS IMPORT: route options modified Mon Oct 14 13:36:01 2019 OPTIONS IMPORT: route-related options modified Mon Oct 14 13:36:01 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Mon Oct 14 13:36:01 2019 OPTIONS IMPORT: peer-id set Mon Oct 14 13:36:01 2019 OPTIONS IMPORT: adjusting link_mtu to 1624 Mon Oct 14 13:36:01 2019 OPTIONS IMPORT: data channel crypto options modified Mon Oct 14 13:36:01 2019 Data Channel: using negotiated cipher 'AES-256-GCM' Mon Oct 14 13:36:01 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Mon Oct 14 13:36:01 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Mon Oct 14 13:36:01 2019 Preserving previous TUN/TAP instance: tun10 Mon Oct 14 13:36:01 2019 NOTE: Pulled options changed on restart, will need to close and reopen TUN/TAP device. Mon Oct 14 13:36:01 2019 /sbin/ip route del 185.107.94.249/32 Mon Oct 14 13:36:01 2019 /sbin/ip route del 0.0.0.0/1 Mon Oct 14 13:36:01 2019 /sbin/ip route del 128.0.0.0/1 Mon Oct 14 13:36:01 2019 Closing TUN/TAP interface Mon Oct 14 13:36:01 2019 /sbin/ip addr del dev tun10 10.8.0.29/16 Mon Oct 14 13:36:01 2019 /etc/openvpn/tunnelDown.sh tun10 1500 1552 10.8.0.29 255.255.0.0 init Mon Oct 14 13:36:02 2019 ROUTE_GATEWAY 172.18.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:12:00:0b Mon Oct 14 13:36:02 2019 TUN/TAP device tun10 opened Mon Oct 14 13:36:02 2019 TUN/TAP TX queue length set to 100 Mon Oct 14 13:36:02 2019 /sbin/ip link set dev tun10 up mtu 1500 Mon Oct 14 13:36:02 2019 /sbin/ip addr add dev tun10 10.8.0.15/16 broadcast 10.8.255.255 Mon Oct 14 13:36:02 2019 /etc/openvpn/tunnelUp.sh tun10 1500 1552 10.8.0.15 255.255.0.0 init Up script executed with tun10 1500 1552 10.8.0.15 255.255.0.0 init Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun10 : 10.8.0.15 Generating transmission settings.json from env variables sed'ing True to true Enforcing ownership on transmission config directories Applying permissions to transmission config directories Setting owner for transmission paths to 1000:122 Setting permission for files (644) and directories (755) '------------------------------------- Transmission will run as '------------------------------------- User name: abc User uid: 1000 User gid: 122 '-------------------------------------

STARTING TRANSMISSION NO PORT UPDATER FOR THIS PROVIDER Transmission startup script complete. STARTING TINYPROXY Found config file /etc/tinyproxy.conf, updating settings. Setting tinyproxy port to 8888 Starting tinyproxy: tinyproxy. Tinyproxy startup script complete. Mon Oct 14 13:36:02 2019 /sbin/ip route add 185.107.94.249/32 via 172.18.0.1 Mon Oct 14 13:36:02 2019 /sbin/ip route add 0.0.0.0/1 via 10.8.0.1 Mon Oct 14 13:36:02 2019 /sbin/ip route add 128.0.0.0/1 via 10.8.0.1 Mon Oct 14 13:36:02 2019 Initialization Sequence Completed

Host system:

Ubuntu 18.04.3 LTS Docker 19.03.3 Docker-Compose 1.24.0

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 4 years ago

Note: The stale bot was recently added to this project to help weed out outdated issues. This will help us to focus time and energy on issues that are important and move the others out of the way. There could however be many issues that are still relevant but have gotten old without ever being fixed. As this is the first round of cleaning it might have been too eager. Feel free to re-open this issue if you think it deserves another look.