Replies: 2 comments 1 reply
-
You have the subnet set to 192.168.11.0 but in transmission you have set your LOCAL_NETWORK: 192.168.3.0/24 |
Beta Was this translation helpful? Give feedback.
1 reply
-
to wrap this up - it worked once I found out the internal IP of the Transmission-container on the respective network (usually in the range 172.17.0.0). I then realized that docker containers on the same network can talk to eachother using their name ("transmission-vpn" in my case). Using this as the hostname in the radarr/sonarr settings worked perfectly. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello all,
after setting up a new docker server following the very detailed tutorial of Anand at smarthomebeginner.com I am having trouble connecting my transmission-vpn to radarr and sonarr. I get the error "Unable to connect to Transmission".
radarr log says:
this is my main docker compose file:
and here are the compose files for transmission, radarr and sonarr:
I feel like it may have something to do with socket-proxy but when I comment out the network socket_proxy in all three compose files, nothing changes.
Any ideas would be welcome!
Beta Was this translation helpful? Give feedback.
All reactions