Since around a week ago, when I try to open the web interface, I get the error "ERR_TOO_MANY_RETRIES". It does not happen when I try through an Incognito Chrome window. Searched web and found some comments related to credentials. So I removed the following three RPC authorization lines from the Docker Run config and the issue stopped.
-e "TRANSMISSION_RPC_AUTHENTICATION_REQUIRED=true" \
-e "TRANSMISSION_RPC_PASSWORD=XXXXXX" \
-e "TRANSMISSION_RPC_USERNAME=XXXXXX" \
Expected Behavior
Be able to use authorization credentials even without Incognito Mode
How have you tried to solve the problem?
Removed the RPC credentials lines and worked around the issue
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: PUREVPN
Running with VPN_CONFIG_SOURCE auto
No bundled config script found for PUREVPN. Defaulting to external config
Already up to date.
Already on 'main'
Your branch is up to date with 'origin/main'.
Found configs for PUREVPN in /config/vpn-configs-contrib/openvpn/purevpn, will replace current content in /etc/openvpn/purevpn
Starting OpenVPN using config nl2-ovpn-udp.ovpn
Modifying /etc/openvpn/purevpn/nl2-ovpn-udp.ovpn for best behaviour in this container
Modification: Point auth-user-pass option to the username/password file
Modification: Change ca certificate path
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.46.0/24 via 172.17.0.1 dev eth0
2024-10-28 14:56:28 OpenVPN 2.5.9 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 29 2023
2024-10-28 14:56:28 library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10
2024-10-28 14:56:28 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2024-10-28 14:56:28 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2024-10-28 14:56:28 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2024-10-28 14:56:28 TCP/UDP: Preserving recently used remote address: [AF_INET]5.254.70.211:53
2024-10-28 14:56:28 Socket Buffers: R=[212992->212992] S=[212992->212992]
2024-10-28 14:56:28 UDP link local: (not bound)
2024-10-28 14:56:28 UDP link remote: [AF_INET]5.254.70.211:53
2024-10-28 14:56:28 TLS: Initial packet from [AF_INET]5.254.70.211:53, sid=fbeeea0b c9e5933b
2024-10-28 14:56:28 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2024-10-28 14:56:29 VERIFY OK: depth=1, C=HK, ST=Central, L=HK, O=Secure-ServerCA, OU=IT, CN=Secure-ServerCA, name=Secure-ServerCA, emailAddress=mail@host.domain
2024-10-28 14:56:29 VERIFY KU OK
2024-10-28 14:56:29 Validating certificate extended key usage
2024-10-28 14:56:29 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2024-10-28 14:56:29 VERIFY EKU OK
2024-10-28 14:56:29 VERIFY OK: depth=0, C=HK, ST=Central, L=HK, O=Secure-Server, OU=IT, CN=Secure-Server, name=changeme, emailAddress=mail@host.domain
2024-10-28 14:56:29 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1557', remote='link-mtu 1549'
2024-10-28 14:56:29 WARNING: 'auth' is used inconsistently, local='auth SHA1', remote='auth [null-digest]'
2024-10-28 14:56:29 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA256
2024-10-28 14:56:29 [Secure-Server] Peer Connection Initiated with [AF_INET]5.254.70.211:53
2024-10-28 14:56:29 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 5.254.26.44,dhcp-option DNS 5.254.26.46,sndbuf 393216,rcvbuf 393216,route-gateway 10.5.12.1,topology subnet,ping 10,ping-restart 120,ifconfig 10.5.12.11 255.255.255.0,peer-id 6,cipher AES-256-GCM'
2024-10-28 14:56:29 Pushed option removed by filter: 'ping 10'
2024-10-28 14:56:29 Pushed option removed by filter: 'ping-restart 120'
2024-10-28 14:56:29 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
2024-10-28 14:56:29 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
2024-10-28 14:56:29 TUN/TAP device tun0 opened
2024-10-28 14:56:29 net_iface_mtu_set: mtu 1500 for tun0
Up script executed with device=tun0 ifconfig_local=10.5.12.11
Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.5.12.11
Enforcing ownership on transmission directories
Applying permissions to transmission directories
Setting owner for transmission paths to 1026:100
Setting permissions for download and incomplete directories
umask: 2
Directories: 775
Files: 664
Setting permission for watch directory (775) and its files (664)
Updating Transmission settings.json with values from env variables
Attempting to use existing settings.json for Transmission
Successfully used existing settings.json /data/transmission-home/settings.json
sed'ing True to true
STARTING TRANSMISSION
Transmission startup script complete.
2024-10-28 14:56:30 Initialization Sequence Completed
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
docker run -d \ --cap-add=NET_ADMIN \ --device=/dev/net/tun \ --restart=unless-stopped \ -v /volume2/Media/Zoned/incomplete/:/data \ -v /volume1/scripts/dockers/transmission/scripts:/scripts \ -v /volume1/scripts/dockers/transmission/configs:/config \ -e "TRANSMISSION_RPC_AUTHENTICATION_REQUIRED=true" \ -e "TRANSMISSION_RPC_PASSWORD=XXXXXX" \ -e "TRANSMISSION_RPC_USERNAME=XXXXXX" \ -e "TRANSMISSION_RPC_ENABLED=true" \ -e "OPENVPN_PROVIDER=PUREVPN" \ -e "OPENVPN_CONFIG=nl2-ovpn-udp" \ -e "OPENVPN_USERNAME=XXXXXX" \ -e "OPENVPN_PASSWORD=XXXXXX" \ -e "TRANSMISSION_HOME=/config/transmission-home" \ -e "LOCAL_NETWORK=192.168.46.0/24" \ -e "CONFIG_MOD_PING=0" \ -e "OPENVPN_OPTS=--inactive 3600 --ping 10 --mute-replay-warnings --pull-filter ignore ping --float --tls-cipher DEFAULT:@SECLEVEL=0 --data-ciphers-fallback 'AES-256-CBC'" \ -e "PGID=100" \ -e "PUID=1026" \ -e "UFW_ALLOW_GW_NET=true" \ -p 9091:9091 \ --dns 8.8.8.8 \ --dns 8.8.4.4 \ --sysctl net.ipv6.conf.all.disable_ipv6=1 \ --name "transmission-openvpn-syno" \ haugene/transmission-openvpn:latest
Current Behavior
Since around a week ago, when I try to open the web interface, I get the error "ERR_TOO_MANY_RETRIES". It does not happen when I try through an Incognito Chrome window. Searched web and found some comments related to credentials. So I removed the following three RPC authorization lines from the Docker Run config and the issue stopped. -e "TRANSMISSION_RPC_AUTHENTICATION_REQUIRED=true" \ -e "TRANSMISSION_RPC_PASSWORD=XXXXXX" \ -e "TRANSMISSION_RPC_USERNAME=XXXXXX" \
Expected Behavior
Be able to use authorization credentials even without Incognito Mode
How have you tried to solve the problem?
Removed the RPC credentials lines and worked around the issue
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: PUREVPN Running with VPN_CONFIG_SOURCE auto No bundled config script found for PUREVPN. Defaulting to external config Already up to date. Already on 'main' Your branch is up to date with 'origin/main'. Found configs for PUREVPN in /config/vpn-configs-contrib/openvpn/purevpn, will replace current content in /etc/openvpn/purevpn Starting OpenVPN using config nl2-ovpn-udp.ovpn Modifying /etc/openvpn/purevpn/nl2-ovpn-udp.ovpn for best behaviour in this container Modification: Point auth-user-pass option to the username/password file Modification: Change ca certificate path 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.46.0/24 via 172.17.0.1 dev eth0 2024-10-28 14:56:28 OpenVPN 2.5.9 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 29 2023 2024-10-28 14:56:28 library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10 2024-10-28 14:56:28 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2024-10-28 14:56:28 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication 2024-10-28 14:56:28 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication 2024-10-28 14:56:28 TCP/UDP: Preserving recently used remote address: [AF_INET]5.254.70.211:53 2024-10-28 14:56:28 Socket Buffers: R=[212992->212992] S=[212992->212992] 2024-10-28 14:56:28 UDP link local: (not bound) 2024-10-28 14:56:28 UDP link remote: [AF_INET]5.254.70.211:53 2024-10-28 14:56:28 TLS: Initial packet from [AF_INET]5.254.70.211:53, sid=fbeeea0b c9e5933b 2024-10-28 14:56:28 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this 2024-10-28 14:56:29 VERIFY OK: depth=1, C=HK, ST=Central, L=HK, O=Secure-ServerCA, OU=IT, CN=Secure-ServerCA, name=Secure-ServerCA, emailAddress=mail@host.domain 2024-10-28 14:56:29 VERIFY KU OK 2024-10-28 14:56:29 Validating certificate extended key usage 2024-10-28 14:56:29 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication 2024-10-28 14:56:29 VERIFY EKU OK 2024-10-28 14:56:29 VERIFY OK: depth=0, C=HK, ST=Central, L=HK, O=Secure-Server, OU=IT, CN=Secure-Server, name=changeme, emailAddress=mail@host.domain 2024-10-28 14:56:29 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1557', remote='link-mtu 1549' 2024-10-28 14:56:29 WARNING: 'auth' is used inconsistently, local='auth SHA1', remote='auth [null-digest]' 2024-10-28 14:56:29 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA256 2024-10-28 14:56:29 [Secure-Server] Peer Connection Initiated with [AF_INET]5.254.70.211:53 2024-10-28 14:56:29 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 5.254.26.44,dhcp-option DNS 5.254.26.46,sndbuf 393216,rcvbuf 393216,route-gateway 10.5.12.1,topology subnet,ping 10,ping-restart 120,ifconfig 10.5.12.11 255.255.255.0,peer-id 6,cipher AES-256-GCM' 2024-10-28 14:56:29 Pushed option removed by filter: 'ping 10' 2024-10-28 14:56:29 Pushed option removed by filter: 'ping-restart 120' 2024-10-28 14:56:29 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key 2024-10-28 14:56:29 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key 2024-10-28 14:56:29 TUN/TAP device tun0 opened 2024-10-28 14:56:29 net_iface_mtu_set: mtu 1500 for tun0 Up script executed with device=tun0 ifconfig_local=10.5.12.11 Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.5.12.11 Enforcing ownership on transmission directories Applying permissions to transmission directories Setting owner for transmission paths to 1026:100 Setting permissions for download and incomplete directories umask: 2 Directories: 775 Files: 664 Setting permission for watch directory (775) and its files (664)
Updating Transmission settings.json with values from env variables Attempting to use existing settings.json for Transmission Successfully used existing settings.json /data/transmission-home/settings.json sed'ing True to true STARTING TRANSMISSION Transmission startup script complete. 2024-10-28 14:56:30 Initialization Sequence Completed
HW/SW Environment
Anything else?
Nothing else.