Sonarr API Timeout Error with nzbgeek

[markmark46]

Evening gents,

Running into an issue with my API timing out. Reset it and it’s been doing this all day. It’s only with nzbgeek and their site appears up and I have posted to their forums regarding this issue. Any help would be appreciated.

I am using Sonarr Version 2.0.0.4472 and it throws me this error:

[code]Unable to connect to indexer, check the log for more details.

Invalid request Validation failed:
– Unable to connect to indexer, check the log for more details[/code]

and

[code]Unable to connect to indexer: The operation has timed out

System.Net.WebException: The operation has timed out
at System.Net.HttpWebRequest.GetResponse()
at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse(HttpRequest request, CookieContainer cookies) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:line 74
at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse(HttpRequest request, CookieContainer cookies) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Common\Http\Dispatchers\FallbackHttpDispatcher.cs:line 58
at NzbDrone.Common.Http.HttpClient.Execute(HttpRequest request) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Common\Http\HttpClient.cs:line 63
at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchIndexerResponse(IndexerRequest request) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:line 297 at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:line 283
at NzbDrone.Core.Indexers.HttpIndexerBase`1.TestConnection() in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:line 310[/code]

Thanks!
M

[Cipherswitch]

Im in the same exact boat. Whats weird is that I have an already configured Sonarr running the same version (2.0.0.4472 ) and running NZBgeek just fine, even when testing, it passes right away. Im trying to setup a new machine for a friend and it just times out, even when using my own api key.

[markus101]

If you look at ((debug logs)) you can see the URL Sonarr is using, which you can paste into a browser, set the API Key and try to load it.

Timeout means your indexer didn’t respond in 30 seconds, not likely related to the API Key, but almost certainly an issue on their side.

[rafuz]

Same problem here:

17-2-23 09:53:09.2|Debug|Api|[GET] /api/config/naming/samples?renameEpisodes=true&replaceIllegalCharacters=true&multiEpisodeStyle=3&stan
dardEpisodeFormat=%7BSeries+Title%7D+-+S%7Bseason%3A00%7DE%7Bepisode%3A00%7D+-+%7BEpisode+Title%7D+%7BQuality+Full%7D&dailyEpisodeFormat
=%7BSeries+Title%7D+-+%7BAir-Date%7D+-+%7BEpisode+Title%7D+%7BQuality+Full%7D&animeEpisodeFormat=%7BSeries+Title%7D+-+S%7Bseason%3A00%7D
E%7Bepisode%3A00%7D+-+%7BEpisode+Title%7D+%7BQuality+Full%7D&seriesFolderFormat=%7BSeries+Title%7D&seasonFolderFormat=Season+%7Bseason%3
A00%7D&includeSeriesTitle=false&includeEpisodeTitle=false&includeQuality=false&replaceSpaces=true&separator=+-+&numberStyle=S%7Bseason%3
A00%7DE%7Bepisode%3A00%7D&id=1: 200.OK (39 ms)
17-2-23 09:53:09.3|Debug|Api|[GET] /api/qualitydefinition: 200.OK (3 ms)
17-2-23 09:53:09.3|Debug|Api|[GET] /api/Restriction: 200.OK (7 ms)
17-2-23 09:53:09.3|Debug|Api|[GET] /api/remotePathMapping: 200.OK (9 ms)
17-2-23 09:53:09.3|Debug|Api|[GET] /api/downloadclient: 200.OK (16 ms)
17-2-23 09:53:09.3|Debug|Api|[GET] /api/indexer: 200.OK (41 ms)
17-2-23 09:53:09.3|Debug|Api|[GET] /api/metadata: 200.OK (21 ms)
17-2-23 09:53:12.9|Debug|Api|[GET] /api/indexer/schema: 200.OK (15 ms)
17-2-23 09:53:36.1|Debug|Newznab|Downloading Feed https://api.nzbgeek.info/api?t=tvsearch&cat=5030,5040,5070&extended=1&apikey=(removed)
&offset=0&limit=100
17-2-23 09:54:11.7|Debug|SabnzbdProxy|Url: http://localhost:8080/api?mode=queue&start=0&limit=0&apikey=(removed)&output=json
17-2-23 09:54:11.7|Debug|SabnzbdProxy|Url: http://localhost:8080/api?mode=history&start=0&limit=30&category=tv&apikey=(removed)&output=j
son
17-2-23 09:54:11.8|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (5 ms)
17-2-23 09:55:11.9|Debug|SabnzbdProxy|Url: http://localhost:8080/api?mode=queue&start=0&limit=0&apikey=(removed)&output=json
17-2-23 09:55:11.9|Debug|SabnzbdProxy|Url: http://localhost:8080/api?mode=history&start=0&limit=30&category=tv&apikey=(removed)&output=j
son
17-2-23 09:55:12.1|Debug|Api|[GET] /api/queue?sort_by=timeleft&order=asc: 200.OK (10 ms)
17-2-23 09:55:16.1|Warn|Newznab|Unable to connect to indexer

[v2.0.0.4613] System.Net.WebException: The request timed out
  at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) <0x415bfc00 + 0x00197> in <filename unknown>:0
  at System.Net.HttpWebRequest.GetResponse () <0x415bd920 + 0x0005a> in <filename unknown>:0
  at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieCont
ainer cookies) [0x000fb] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:63

17-2-23 09:55:16.1|Warn|NzbDroneErrorPipeline|Invalid request Validation failed:
 -- Unable to connect to indexer, check the log for more details
17-2-23 09:55:16.1|Debug|Api|[POST] /api/indexer/test: 400.BadRequest (100055 ms)

If I do a curl from my system

curl https://api.nzbgeek.info/api?t=tvsearch&cat=5030,5040,5070&extended=1&apikey=<apikey>&offset=0&limit=100
[1] 3493
[2] 3494
[3] 3495
[4] 3496
[5] 3497
[2]   Done                    cat=5030,5040,5070
[3]   Done                    extended=1

Connection seems ok but I can’t understand why I get a timeout in Sonarr.
Someone could help?

Fixed, I had to restar the sonarr system service.
Restarting inside the UI did not cleared the situation.