Unable to connect to indexer: HTTP request failed: [400:BadRequest] [GET]

Sonarr version (exact version): 4.0.0.642 (was recently on v3 but tried v4 to test)
Description of issue:

I understand this may not be directly related to Sonarr as it also appears to occur on Radarr. Anything to help point me in the right direction is greatly appreciated.

  • I’m running Sonarr locally and is not externally accessible.
  • I’m running Jackett on a external server hosted elsewhere.
  • Sonarr connects to the indexers via Jackett.

Unfortunately with this configuration, Indexers will often appear in Sonarr with the following error:

Unable to connect to indexer: HTTP request failed: [400:BadRequest] [GET]

What’s interesting is it appears only when doing an auto search but does not occur with manual searching. It appears manual searches retrieves its results from Jackett’s cache? But automatic searching produces these errors.

Here’s the rest of the error:

NzbDrone.Common.Http.HttpException: HTTP request failed: [400:BadRequest] [GET] at [https://(redacted)/jackett/api/v2.0/indexers/(redacted)/results/torznab/api?t=tvsearch&cat=5000,5040&extended=1&apikey=(redacted)&offset=0&limit=100]
at NzbDrone.Common.Http.HttpClient.ExecuteAsync(HttpRequest request) in ./Sonarr.Common/Http/HttpClient.cs:line 119
at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchIndexerResponse(IndexerRequest request) in ./Sonarr.Core/Indexers/HttpIndexerBase.cs:line 354 at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in ./Sonarr.Core/Indexers/HttpIndexerBase.cs:line 338
at NzbDrone.Core.Indexers.HttpIndexerBase`1.TestConnection() in ./Sonarr.Core/Indexers/HttpIndexerBase.cs:line 374

<?xml version="1.0" encoding="UTF-8"?>

If Sonarr’s debug/trace logs don’t have additional information about the request then hopefully Jackett’s do because for some reason it doesn’t like the request Sonarr is making.

I recently upgraded the machine that these containers were hosted on to a M.2 NVMe drive and the issues corrected itself. I wonder if it was performance related.

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