"All indexers are unavailable due to failures"

Help & Support
#1

Suddenly recieved this message on all my sonarr indexers and they now consistently now dont work after years of being fine. Picking one of them, the logs show: (note double slash in first URL) for the nzbndx.com usenet indexer

[v2.0.0.4949] System.ArgumentException: Uri didn’t match expected pattern: https://nzbndx.com//api?t=tvsearch&cat=5030,5040&extended=1&apikey=(removed)&offset=0&limit=100
at NzbDrone.Common.Http.HttpUri.Parse() in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpUri.cs:line 83
at NzbDrone.Common.Http.HttpClient.Execute(HttpRequest request) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:line 55
at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchIndexerResponse(IndexerRequest request) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:line 302 at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:line 288
at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchReleases(Func2 pageableRequestChainSelector, Boolean isRecent) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:line 133

I mailed nzbndx.com support and they pointed out the double slash issue. I ran the ‘test’ function in Sonarr and I get the same error with the //

There a few similar reports, saying “fix the URI” but They;re setup just fine in my system and I dont know how to just “fix the URI”. Any help appreciated.

17-10-17 22:29:43.7|Info|RssSyncService|Starting RSS Sync
17-10-17 22:29:43.8|Warn|FetchAndParseRssService|No available indexers. check your configuration.
17-10-17 22:29:43.8|Info|DownloadDecisionMaker|No results found
17-10-17 22:29:43.8|Info|RssSyncService|RSS Sync Completed. Reports found: 0, Reports grabbed: 0
17-10-17 22:29:46.5|Warn|Newznab|Unable to connect to indexer

[v2.0.0.4949] System.ArgumentException: Uri didn’t match expected pattern: https://nzbndx.com//api?t=caps&apikey=(removed) at NzbDrone.Common.Http.HttpUri.Parse() in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpUri.cs:line 83
at NzbDrone.Common.Http.HttpClient.Execute(HttpRequest request) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:line 55
at NzbDrone.Common.Http.HttpClient.Get(HttpRequest request) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:line 220
at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.FetchCapabilities(NewznabSettings indexerSettings) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:line 62
at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.<>c__DisplayClass4_0.b__0() in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:line 35
at NzbDrone.Common.Cache.Cached1.Get(String key, Func1 function, Nullable1 lifeTime) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Cache\Cached.cs:line 81 at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.GetCapabilities(NewznabSettings indexerSettings) in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:line 35 at NzbDrone.Core.Indexers.Newznab.Newznab.get_PageSize() in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Indexers\Newznab\Newznab.cs:line 22 at NzbDrone.Core.Indexers.Newznab.Newznab.GetRequestGenerator() in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Indexers\Newznab\Newznab.cs:line 26 at NzbDrone.Core.Indexers.HttpIndexerBase1.TestConnection() in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:line 315

17-10-17 22:29:46.5|Warn|NzbDroneErrorPipeline|Invalid request Validation failed:
– Unable to connect to indexer, check the log for more details

#2

I’ve got the same issue here with the exact same error. Looks like it might be due to the extra forward slash in the URL? I removing the trailing forward slash in the settings for nzbndx does not fix it, either.

#3

Removing the trailing slash from the URL doesn’t fix it?

2.0.0.4949 isn’t a new release, did you just up to it?

#4

Removing the trailing slash gives same result.

Its the version on here: https://sonarr.tv/#download (windows)

Havent upgraded in months, happy with it up until this event.

#5

Can you post the full ((trace log)) of a test (to pastebin/hastebin/something similar) so we can take a look?

#7

Sure

https://pastebin.com/GPH87cLX

both log files are in here.

I only really use the nzbndx.com indexer now.

#8

Switching the URL to https://nzbndx.com should take care of it.

It looks like the request to http://nzbndx.com/api?t=caps&apikey=(removed) is redirected to https://nzbndx.com//api?t=caps&apikey=(removed). Note the double slash is added with the redirect, which is a problem with their configuration and I see if in the browser as well, though the browser is a bit more lenient.

#9

doh. so simple. Thankyou thats worked!

#11

And now its stopped again. Worked for a little while with the HTTPS - at least enough to test, but now gives exactly the same error as before. I’ll contact the site support with this information,

Aha - for reference, this now works: https://nzbndx.com/api including the /api does the trick.

#12

/api should be part of the URL base. If it’s part of the URL and URL Base it’ll be duplicated.

#13

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