Radarr/Sonarr works with deluge but not qbittorrent or transmission with same platform

Help & Support
1

Sonarr version (exact version): 4.0.13.2932-ls272
Mono version (if Sonarr is not running on Windows): .NET
Yes (6.0.13)
OS: Docker container / Alpine
Debug logs: None
Description of issue: Cannot connect to qbittorrent or transmission as download client.

I have sonarr and radarr in containers on Server A and download clients running in containers on Server B. When I set up a deluge container on Server B, sonarr connects to it fine, I can get to the web console, etc. However, when I set up either qbittorrent or transmission on Server B, sonarr highlights the host field in red and indicates that it cannot connect. In all cases I am using the ip address of Server B as the host name, and in all cases I can get to the web console of the qbittorrent/transmission as expected but Sonarr/Radarr will not connect.

The problem is that Deluge seems bloated and has problems if there are a lot of connections and I would prefer to use qbittorrent as the downloader. I have been reading a lot on this issue and some people have said that a setting Settings → WebUI → remote control should be set but I can see no such setting. In all cases I am using the latest contrainers:

linuxserver/sonarr:latest
linuxserver/radarr:latest
linuxserver/qbittorrent:latest
linuxserver/transmission:latest
linuxserver/deluge:latest

2

Since everything is in containers have you set up the containers to use the proper network and port ? You say you are using the ServerB IP address but if the container is not hooked up to the right network interface you won’t be able to connect. Also if you have a firewall you need to enable the docker container network to be able to access it. I am using qbittorrent with sonarr both in docker containers and they weren’t able to see eachother in the begining so I had to open my firewall for each container network since I have DENY ALL rule in the firewall. As for the remote control its the first thing in WEBUI you need to put in the port that’s it .

3

If it was the containers that were the issue then Deluge wouldn’t work. Everything is on the bridged network and there is no firewall.

Update: So I decided to put qbittorrent on server B and it worked. My best guess is that the VPN on server A was allowing TCP through but not UDP. I had the whole subnet whitelisted but maybe it didn’t cover UDP. qbittorrent uses UDP but deluge does not. This is the only difference I can think of that putting it on the same server would make.

4

:slight_smile: you didn’t say anything about a VPN :slight_smile: Glad you figured it out but qbittorent can use TCP I suggest you change it is more secured for torrenting. It’s in connection menu first thing :slight_smile: .