Troubleshooting the Sonarr and Jackett relationship?

Help & Support
1

Last weekend my Jackett/Sonarr configuration ceased working entirely. Jackett is able to successfully test all my configured trackers, view cached releases, and search manually with no issues. CouchPotato also does not appear to be having any issues with Jackett/torznab.

However, Sonarr reports that every Jackett/torznab connection is “unavailable due to failures” Sonarr’s log spits out the following over and over:

Speed.cd server is currently unavailable. http://10.0.10.15:9117/torznab/speedcd/api?t=tvsearch&cat=5030,5040&extended=1&apikey=<removed>&offset=0&limit=100 The request timed out    

TorrentLeech server is currently unavailable. http://10.0.10.15:9117/torznab/torrentleech/api?t=tvsearch&cat=5000,5030,5040,5080,5070&extended=1&apikey=<removed>&offset=0&limit=100 The request timed out

MoreThan.TV server is currently unavailable. http://10.0.10.15:9117/torznab/morethantv/api?t=tvsearch&cat=5030,5040&extended=1&apikey=<removed>&offset=0&limit=100 The request timed out

I’ve removed and reconfigured each tracker in Jackett just in case and have verified the API keys and configuration a bunch of times. What else can I try to get things moving again?
Thanks in advance for your help!

2

Are you running Sonarr and jacket on the same machine? If so, try changing the ip address to 127.0.0.1

3

Thanks for the reply! Before getting your reply, I ended up deleting both setups and starting from scratch. It appears to be working again.

Hopefully this won’t happen again, but if it does, I’ll try your local IP suggestion first.

4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.