Dockerized client cannont connect Transmission

Help & Support
#1

Version 2.0.0.5322

Mono Version 5.20.1.19
TOS 4 (Terramaster NAS)
LOGS https://justpaste.it/6wamo
Hi,
I have both transmission and sonarr running on docker containers, both applications runs ok, and share the same IP address, 192.168.1.43
I can connect to transmission web interface from my computer on address [http://192.168.1.43:9091/transmission/web] and to sonarr on address [http://192.168.1.43:44358] so when I try to configure transmission as my download client in sonarr I put 192.168.1.43 on address, 9091 on port , my username and my password for rpc as configured on setting.json file but when I test the connection it fails, on logs it says connection timeout,
I tried to use localhost on address then the error message is ConnectFailure (Connection refused)
I also tried to disable rpc authentication and the problem is the same.

Any help would be appreciate.

#2

if i remember correctly some docker network types cant go up to the host and then back down into the same docker network

can you post the docker files/commands for both containers?

if theyre on the same docker network then you can set a hostname as part of the command/docker file, and then use that as the hostname to connect to on the actual container (not host) port.

eg, if you had transmission set to use transmission as its hostname then in sonarr you would use a hostname of transmission and a port of 9091 (presuming no mapping) and it would just work

#3

Thanks rhom, just using container name as hostname sonarr was able to connect.

#4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.