Cant access/load WebUI, Tests show transmission is running

[tjenvy]

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

docker run --cap-add=NET_ADMIN --name Transmission -d --restart=always
-v /Volumes/Storage/Users/tjenvy/MediaData/transmission:/config
-e OPENVPN_PROVIDER=pia
-e OPENVPN_USERNAME=redacted
-e OPENVPN_PASSWORD=redacted
-e DISABLE_PORT_UPDATER=true
-e OPENVPN_CONFIG=us_washington_dc
-e TZ=America/New_York
-v /Volumes/Media12Main:/MediaMain12
-e LOCAL_NETWORK=10.0.0.0/16
-e TRANSMISSION_WEB_UI=flood-for-transmission
--log-driver json-file
--log-opt max-size=10m
-p 9091:9091
haugene/transmission-openvpn

Current Behavior

Container starts fine. No errors, logs show running. localhost:9091 or 10.0.1.100:9091 never loads.
Other containers using this system cant access get authentication failed because they cant pass data to transmission.

Expected Behavior

Web loads and other containers can speak to the system.

How have you tried to solve the problem?

Let me start by saying nothing on my system has changed no system updates no browser updates no updates to Docker nothing.
A few days ago, I noticed that I could no longer access the Transmission web UI. I killed the docker container and restarted it still same thing.
I then trashed the container and spun up a new one same thing.
I then deleted the image and downloaded a fresh copy and spun up a new container again same issue
All of my Docker run command everything has been working for years without any issue.
I read through the articles and did the test within the running container and I do get the basic message that allows you to know that the container is running and the transmission is running.
Any other container I have that connects into it for downloading says that it can't reach it and that authentication failed of course.
I've completely used a brand new directory structure with a very basic Docker run command and even with that I still can't access anything.
The only thing I have not tried is creating a new user on my Mac and trying it there.
What I don't understand is that there's nothing in the logs showing that there's any errors in the logs look just like they have for the past few years. With no changes to the system I'm kind of up in the air here on what to do.
Let me emphasize that everything has been functioning exactly how it looks for years without any issue.

Log output

2025-04-11 14:24:07 Starting container with revision: 07f5a2b
2025-04-11 14:24:07 TRANSMISSION_HOME is currently set to: /config/transmission-home
2025-04-11 14:24:07 Creating TUN device /dev/net/tun
2025-04-11 14:24:07 Using OpenVPN provider: PIA
2025-04-11 14:24:07 Running with VPN_CONFIG_SOURCE auto
2025-04-11 14:24:07 Provider PIA has a bundled setup script. Defaulting to internal config
2025-04-11 14:24:07 Executing setup script for pia
2025-04-11 14:24:07 Downloading OpenVPN config bundle openvpn into temporary file /tmp/tmp.c6EtRSYZgS
2025-04-11 14:24:07 Extract OpenVPN config bundle into PIA directory /etc/openvpn/pia
2025-04-11 14:24:07 Starting OpenVPN using config us_washington_dc.ovpn
2025-04-11 14:24:07 Modifying /etc/openvpn/pia/us_washington_dc.ovpn for best behaviour in this container
2025-04-11 14:24:07 Modification: Point auth-user-pass option to the username/password file
2025-04-11 14:24:07 Modification: Change ca certificate path
2025-04-11 14:24:07 Modification: Change ping options
2025-04-11 14:24:07 Modification: Update/set resolv-retry to 15 seconds
2025-04-11 14:24:07 Modification: Change tls-crypt keyfile path
2025-04-11 14:24:07 Modification: Set output verbosity to 3
2025-04-11 14:24:07 Modification: Remap SIGUSR1 signal to SIGTERM, avoid OpenVPN restart loop
2025-04-11 14:24:07 Modification: Updating status for config failure detection
2025-04-11 14:24:07 Setting OpenVPN credentials...
2025-04-11 14:24:07 adding route to local network 10.0.0.0/16 via 172.17.0.1 dev eth0
2025-04-11 14:24:07 2025-04-11 14:24:07 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning.
2025-04-11 14:24:07 2025-04-11 14:24:07 OpenVPN 2.5.9 aarch64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 29 2023
2025-04-11 14:24:07 2025-04-11 14:24:07 library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10
2025-04-11 14:24:07 2025-04-11 14:24:07 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2025-04-11 14:24:07 2025-04-11 14:24:07 CRL: loaded 1 CRLs from file -----BEGIN X509 CRL-----
2025-04-11 14:24:07 MIICWDCCAUAwDQYJKoZIhvcNAQENBQAwgegxCzAJBgNVBAYTAlVTMQswCQYDVQQI
2025-04-11 14:24:07 EwJDQTETMBEGA1UEBxMKTG9zQW5nZWxlczEgMB4GA1UEChMXUHJpdmF0ZSBJbnRl
2025-04-11 14:24:07 cm5ldCBBY2Nlc3MxIDAeBgNVBAsTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMSAw
2025-04-11 14:24:07 HgYDVQQDExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4GA1UEKRMXUHJpdmF0
2025-04-11 14:24:07 ZSBJbnRlcm5ldCBBY2Nlc3MxLzAtBgkqhkiG9w0BCQEWIHNlY3VyZUBwcml2YXRl
2025-04-11 14:24:07 aW50ZXJuZXRhY2Nlc3MuY29tFw0xNjA3MDgxOTAwNDZaFw0zNjA3MDMxOTAwNDZa
2025-04-11 14:24:07 MCYwEQIBARcMMTYwNzA4MTkwMDQ2MBECAQYXDDE2MDcwODE5MDA0NjANBgkqhkiG
2025-04-11 14:24:07 9w0BAQ0FAAOCAQEAQZo9X97ci8EcPYu/uK2HB152OZbeZCINmYyluLDOdcSvg6B5
2025-04-11 14:24:07 jI+ffKN3laDvczsG6CxmY3jNyc79XVpEYUnq4rT3FfveW1+Ralf+Vf38HdpwB8EW
2025-04-11 14:24:07 B4hZlQ205+21CALLvZvR8HcPxC9KEnev1mU46wkTiov0EKc+EdRxkj5yMgv0V2Re
2025-04-11 14:24:07 ze7AP+NQ9ykvDScH4eYCsmufNpIjBLhpLE2cuZZXBLcPhuRzVoU3l7A9lvzG9mjA
2025-04-11 14:24:07 5YijHJGHNjlWFqyrn1CfYS6koa4TGEPngBoAziWRbDGdhEgJABHrpoaFYaL61zqy
2025-04-11 14:24:07 MR6jC0K2ps9qyZAN74LEBedEfK7tBOzWMwr58A==
2025-04-11 14:24:07 -----END X509 CRL-----
2025-04-11 14:24:07
2025-04-11 14:24:07 2025-04-11 14:24:07 TCP/UDP: Preserving recently used remote address: [AF_INET]37.19.220.45:1198
2025-04-11 14:24:07 2025-04-11 14:24:07 Socket Buffers: R=[212992->212992] S=[212992->212992]
2025-04-11 14:24:07 2025-04-11 14:24:07 UDP link local: (not bound)
2025-04-11 14:24:07 2025-04-11 14:24:07 UDP link remote: [AF_INET]37.19.220.45:1198
2025-04-11 14:24:07 2025-04-11 14:24:07 TLS: Initial packet from [AF_INET]37.19.220.45:1198, sid=337c3e85 06331317
2025-04-11 14:24:07 2025-04-11 14:24:07 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2025-04-11 14:24:07 2025-04-11 14:24:07 VERIFY OK: depth=1, C=US, ST=CA, L=LosAngeles, O=Private Internet Access, OU=Private Internet Access, CN=Private Internet Access, name=Private Internet Access, emailAddress=secure@privateinternetaccess.com
2025-04-11 14:24:07 2025-04-11 14:24:07 VERIFY KU OK
2025-04-11 14:24:07 2025-04-11 14:24:07 Validating certificate extended key usage
2025-04-11 14:24:07 2025-04-11 14:24:07 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2025-04-11 14:24:07 2025-04-11 14:24:07 VERIFY EKU OK
2025-04-11 14:24:07 2025-04-11 14:24:07 VERIFY OK: depth=0, C=US, ST=CA, L=LosAngeles, O=Private Internet Access, OU=Private Internet Access, CN=washington472, name=washington472
2025-04-11 14:24:07 2025-04-11 14:24:07 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA512
2025-04-11 14:24:07 2025-04-11 14:24:07 [washington472] Peer Connection Initiated with [AF_INET]37.19.220.45:1198
2025-04-11 14:24:07 2025-04-11 14:24:07 PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway def1,route-ipv6 2000::/3,dhcp-option DNS 10.0.0.243,route-gateway 10.44.112.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.44.112.108 255.255.255.0,peer-id 2,cipher AES-128-GCM'
2025-04-11 14:24:07 2025-04-11 14:24:07 OPTIONS IMPORT: timers and/or timeouts modified
2025-04-11 14:24:07 2025-04-11 14:24:07 OPTIONS IMPORT: compression parms modified
2025-04-11 14:24:07 2025-04-11 14:24:07 OPTIONS IMPORT: --ifconfig/up options modified
2025-04-11 14:24:07 2025-04-11 14:24:07 OPTIONS IMPORT: route options modified
2025-04-11 14:24:07 2025-04-11 14:24:07 OPTIONS IMPORT: route-related options modified
2025-04-11 14:24:07 2025-04-11 14:24:07 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
2025-04-11 14:24:07 2025-04-11 14:24:07 OPTIONS IMPORT: peer-id set
2025-04-11 14:24:07 2025-04-11 14:24:07 OPTIONS IMPORT: adjusting link_mtu to 1625
2025-04-11 14:24:07 2025-04-11 14:24:07 OPTIONS IMPORT: data channel crypto options modified
2025-04-11 14:24:07 2025-04-11 14:24:07 Data Channel: using negotiated cipher 'AES-128-GCM'
2025-04-11 14:24:07 2025-04-11 14:24:07 Outgoing Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key
2025-04-11 14:24:07 2025-04-11 14:24:07 Incoming Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key
2025-04-11 14:24:07 2025-04-11 14:24:07 net_route_v4_best_gw query: dst 0.0.0.0
2025-04-11 14:24:07 2025-04-11 14:24:07 net_route_v4_best_gw result: via 172.17.0.1 dev eth0
2025-04-11 14:24:07 2025-04-11 14:24:07 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=fe:6a:59:00:f5:cb
2025-04-11 14:24:07 2025-04-11 14:24:07 GDG6: remote_host_ipv6=n/a
2025-04-11 14:24:07 2025-04-11 14:24:07 net_route_v6_best_gw query: dst ::
2025-04-11 14:24:07 2025-04-11 14:24:07 sitnl_send: rtnl: generic error (-101): Network is unreachable
2025-04-11 14:24:07 2025-04-11 14:24:07 ROUTE6: default_gateway=UNDEF
2025-04-11 14:24:07 2025-04-11 14:24:07 TUN/TAP device tun0 opened
2025-04-11 14:24:07 2025-04-11 14:24:07 net_iface_mtu_set: mtu 1500 for tun0
2025-04-11 14:24:07 2025-04-11 14:24:07 net_iface_up: set tun0 up
2025-04-11 14:24:07 2025-04-11 14:24:07 net_addr_v4_add: 10.44.112.108/24 dev tun0
2025-04-11 14:24:07 2025-04-11 14:24:07 net_route_v4_add: 37.19.220.45/32 via 172.17.0.1 dev [NULL] table 0 metric -1
2025-04-11 14:24:07 2025-04-11 14:24:07 net_route_v4_add: 0.0.0.0/1 via 10.44.112.1 dev [NULL] table 0 metric -1
2025-04-11 14:24:07 2025-04-11 14:24:07 net_route_v4_add: 128.0.0.0/1 via 10.44.112.1 dev [NULL] table 0 metric -1
2025-04-11 14:24:07 2025-04-11 14:24:07 WARNING: OpenVPN was configured to add an IPv6 route. However, no IPv6 has been configured for tun0, therefore the route installation may fail or may not work as expected.
2025-04-11 14:24:07 2025-04-11 14:24:07 add_route_ipv6(2000::/3 -> :: metric -1) dev tun0
2025-04-11 14:24:07 2025-04-11 14:24:07 net_route_v6_add: 2000::/3 via :: dev tun0 table 0 metric -1
2025-04-11 14:24:07 Up script executed with device=tun0 ifconfig_local=10.44.112.108
2025-04-11 14:24:07 Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.44.112.108
2025-04-11 14:24:07 Using Flood for Transmission UI, overriding TRANSMISSION_WEB_HOME
2025-04-11 14:24:07
2025-04-11 14:24:07 -------------------------------------
2025-04-11 14:24:07 Transmission will run as
2025-04-11 14:24:07 -------------------------------------
2025-04-11 14:24:07 User name: root
2025-04-11 14:24:07 User uid: 0
2025-04-11 14:24:07 User gid: 0
2025-04-11 14:24:07 -------------------------------------
2025-04-11 14:24:07
2025-04-11 14:24:07 Updating Transmission settings.json with values from env variables
2025-04-11 14:24:07 Attempting to use existing settings.json for Transmission
2025-04-11 14:24:07 Successfully used existing settings.json /config/transmission-home/settings.json
2025-04-11 14:24:07 Overriding bind-address-ipv4 because TRANSMISSION_BIND_ADDRESS_IPV4 is set to 10.44.112.108
2025-04-11 14:24:07 Overriding download-dir because TRANSMISSION_DOWNLOAD_DIR is set to /data/completed
2025-04-11 14:24:07 Overriding incomplete-dir because TRANSMISSION_INCOMPLETE_DIR is set to /data/incomplete
2025-04-11 14:24:07 Overriding rpc-password because TRANSMISSION_RPC_PASSWORD is set to [REDACTED]
2025-04-11 14:24:07 Overriding rpc-port because TRANSMISSION_RPC_PORT is set to 9091
2025-04-11 14:24:07 Overriding rpc-username because TRANSMISSION_RPC_USERNAME is set to
2025-04-11 14:24:07 Overriding watch-dir because TRANSMISSION_WATCH_DIR is set to /data/watch
2025-04-11 14:24:07 sed'ing True to true
2025-04-11 14:24:07 STARTING TRANSMISSION
2025-04-11 14:24:07 Transmission startup script complete.
2025-04-11 14:24:07 2025-04-11 14:24:07 Initialization Sequence Completed

HW/SW Environment

- OS:macos 15.3
- Docker: Docker Desktop Version 4.39.0 (184744)

Anything else?

No response

[tjenvy]

Also tried in a new user on the same system. no change same behavior.

[tjenvy]

Well as a test, I went back to an older version of Docker 4.19 and everything works.

So yeah, im out of the woods of annoying things not working but still would be interesting to know what is wrong with the new version. happy to test whatever since I know I can use the older one for now.

[mjc-506]

I'm having a similar issue - previously working setup using Docker (Docker version 28.1.1, build 4eba377327) Compose on a Linux server, until last week-ish was able to access the UI on port 9091 from local clients, and now no longer.

Transmission is still running, and I can curl to it on the server, but not any other local clients. LOCAL_NETWORK env is correctly set (and unchanged from previously), and I can access other containers running on the server (otherwise I'd be looking at forwarding)

[GrimalDev]

I have the same problem since I switched my compose definition with transmission in it to a new server. My old server was using docker-ce 27.2.1 while the new server is using 28.2.2. so I have downgraded to the same version. but the issue persists. I've checked the logs, everything is perfect. did anyone solve this?

[Jason954]

Same for me, i switch my compose to another server, same compose, only docker version different.

Got 401 unauthorized when i perform a curl