Sonarr version (exact version): 2.0.0.4146 Mono version (if Sonarr is not running on Windows): Mono version 3.10.0 (mono-3.10.0-branch/ce003f4 Tue Nov 25 20:18:29 UTC 2014) OS: OSMC ((Debug logs)) (posted to hastebin or similar): http://hastebin.com/igofocunic.1c Description of issue: For few weeks I’ve issue with Sonarr which can’t contact deluge to push torrents.
You can see in logs a:
[v2.0.0.4146] NzbDrone.Core.Download.Clients.DownloadClientException: Unable to connect to Deluge, please check your settings —> System.Net.WebException: The request timed out
at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) [0x00000] in :0
But just after I launched a Deluge test and it succeed.
I changed nothing in my settings and it was working at least for a year…
Deluge didn’t respond, this seems to be a pretty common thing with Deluge when Sonarr pushes a torrent to it, it never responds, sometimes (maybe always?) it even queues the torrent and because Sonarr doesn’t know it was successful (because Deluge failed to respond) it tries another one. The test works, but it doesn’t try adding a torrent (it can’t do that in the test) so its not testing the exact same scenario that is failing.
Deluge needs to respond to the torrent add request, in a timely manner (Sonarr waits 10-30 seconds for it to respond if I recall correctly), which should be plenty of time, not sure if waiting longer would work, Deluge’s web API seems unreliable.
@Taloth and I were discussing it and the reasoning is quite dumb from a 3rd party perspective:
it’s actually the connection between the deluge webui/api and the daemon rpc.
if there’s a problem with the request that the webapi makes to the rpc, it just gets dropped… no errors, nada, just an eventual timeout.
Ideally we’d connect directly to the daemon, but thats easier said than done.