I have 2 deluge servers one local and one in a seedbox. I added my local web client to sonarr and everything was working great. Then i decided to add my seedbox url to the local web client connection manager. When Sonarr adds eps via manual and its a torrent, it would add it to the correct deluge client but when sonarr does it auto and finds a torrent, it would add it to the seedbox deluge. Since it fails to communicate (even if the torrent was actually added) it searches again and chooses a nzb torrent. Very odd behavior. But i dont think this is sonarr’s fault because i also use Transdrone and even if it was configured for my local deluge when i would select it, it would connect to my seedbox client. After remove the seedbox URL from the web client connection manager, Transdrone started to show my local client queue again.
Sonarr will only connect to the host that has an IP of 127.0.0.1, so adding a second one should only connect to the local one, unless the Deluge Web Client does something odd with them.
The behaviour is the same between adding a result from a manual search or an RSS sync/automatic search.
It definitely looks like Deluge’s Web client does something wonky and since Sonarr doesn’t support multiple download client I don’t think this is anything for us to do here.