Time out when sending to Deluge, but test succeeds?

[point0]

This started out of the blue about a week ago. I’m unable to send any episodes to deluge for download:

[v2.0.0.4613] NzbDrone.Core.Download.Clients.DownloadClientException: Unable to connect to Deluge, please check your settings ---> System.Net.WebException: The request timed out

Using the gui to test connection to the download client succeeds, and it also appears that some data is coming from the client because I can see it pull a list of the torrents active in Deluge in the log file.

Any ideas?

[markus101]

Deluge’s Web API will at times just stop responding to requests (mainly add requests), no errors come back, but it just doesn’t respond. Try restarting Deluge and the web daemon for it to see if it starts responding properly.

[point0]

Thanks, I’ve done that.

Interestingly, I’ve just set up Radarr with the same settings, and it can send torrents to Deluge with no problem, so I don’t think the issue is on that side.

[markus101]

Could be related to the category or Sonarr is just unable to reach it, but it’s timing out, so Sonarr is never getting a response.

[Taloth]

To explain, Sonarr talks to the deluge webui api, and the webui api talks to the deluge daemon. if the Daemon throws an error, the webui doesn’t actually return the error to us, it just sits there silently till it times out.
So if you want to know what’s going in you’ll have to check the deluge logs (possibly have to enable those).
One example I can think of is that the output path or other parameters configured in the label (in deluge) are invalid.

[point0]

This turned out to be an MTU issue on the server running sonarr. Thanks for the help.

[Taloth]

Wow, I haven’t heard of one of those in ages.

[point0]

You don’t if you leave everything at defaults. That’s where I went wrong.