Sonarr - Cant connect to indexer
TheGreatDoc opened this issue · 19 comments
Im unable to add amarr as indexer, Im getting this error in sonarr:
2023-11-04 12:52:25.9|Warn|HttpClient|HTTP Error - Res: [GET] http://amarr:8080/indexer/aMule/api?t=caps: 404.NotFound (0 bytes)
2023-11-04 12:52:25.9|Warn|Torznab|Unable to connect to indexer
[v3.0.10.1567] NzbDrone.Common.Http.HttpException: HTTP request failed: [404:NotFound] [GET] at [http://amarr:8080/indexer/aMule/api?t=caps]
at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00154] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Common\Http\HttpClient.cs:105
at NzbDrone.Common.Http.HttpClient.Get (NzbDrone.Common.Http.HttpRequest request) [0x00007] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Common\Http\HttpClient.cs:281
at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.FetchCapabilities (NzbDrone.Core.Indexers.Newznab.NewznabSettings indexerSettings) [0x000a1] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:64
at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider+<>c__DisplayClass4_0.<GetCapabilities>b__0 () [0x00000] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:36
at NzbDrone.Common.Cache.Cached`1[T].Get (System.String key, System.Func`1[TResult] function, System.Nullable`1[T] lifeTime) [0x000b1] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Common\Cache\Cached.cs:104
at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.GetCapabilities (NzbDrone.Core.Indexers.Newznab.NewznabSettings indexerSettings) [0x00020] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:36
at NzbDrone.Core.Indexers.Torznab.Torznab.get_PageSize () [0x00000] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Indexers\Torznab\Torznab.cs:23
at NzbDrone.Core.Indexers.Torznab.Torznab.GetRequestGenerator () [0x00000] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Indexers\Torznab\Torznab.cs:27
at NzbDrone.Core.Indexers.HttpIndexerBase`1[TSettings].TestConnection () [0x00007] in C:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:336
2023-11-04 12:52:25.9|Warn|SonarrErrorPipeline|Invalid request Validation failed:
Looks like an issue in the documentation, please try with lowercase amule in the URL:
http://amarr:8080/indexer/amule
It should also work like this:
http://amarr:8080
Is this Radarr or Sonarr? What version?
Sorry, just noticed it's Sonarr, can you tell me the version?
Version
3.0.10.1567
Package Version
3.0.10.1567-ls185 by [linuxserver.io](https://linuxserver.io/)
Mono Version 6.12.0.182
I just saw that amarr is only tested with AdunanzA, and Im running the ngosang/amule
docker image.
Maybe thats the problem?
Nope it should work perfectly with amule standard. There was at least a bug with Sonarr (I'm mainly testing it with Radarr), I just fixed it and should work as soon as version 1.5.3 becomes available (Should be in few minutes)
But will keep this open until I get your confirmation
I can add it now, but only if categories
field is All
and if host is set to http://amarr:8080
If host includes /indexer/amule
or categories is not All, same error happens.
BUT, I dont feel is working correctly. An interactive search for an episode (from Sonarr) doesnt return anything.
Also, I have an episode (the one I've tried to do the interactive search) in the amule queue (as a manual search from amule does return the episode) and its not showing in the Sonarr queue.
This new problem could be an entirely new issue, so Im going to change amarr loglevel to debug and check if something is happening and will let you know
BTW, very thanks for your quick responses!!!!
Update:
I've put amarr in debug mode. When I do a search in Sonarr, nothing happens in the amarr log.
The only I get is some kind of queue update (which doesnt show in Sonarr queue)
Do you want me to pastebin the amarr debug log?
@TheGreatDoc hey, when you open the aMule UI, have you tried connecting to a different aMule server? Is the server giving back to you a high id or a low id? (you chs check that on the bottom right bar giving you the connection status).
Connecting to a different server fixed the issue to me, and I was able to get results back from any "Search" done in radarr. For sonarr probably it's the same
@Marcosaurios Yes, I have high id and tried different servers.
I just tested in radarr and it works correctly, but in sonarr it doesnt.
@vexdev Maybe you could take a look to that?
Have the same issue in sonarr. Tried some v3 setup (didn't check exact version) and v4.0.0.733.
In the logs I can find this error:
|Debug|NewznabRequestGenerator|Indexer capabilities lacking season & ep query parameters, no Standard series search possible: amarr
So it seems for sonarr to work the indexer needs extra features that are currently not there.
Working fine with radarr, lidarr and readarr
Same problem here,works fine with radarr but not with sonarr 😞
Same here
Hi all, a quick update: looks like Sonarr is expecting a slightly different API than Radarr is. I'm working on the compatibility and I believe this should fix it for Lidarr as well. Will keep you posted in the next days
Good news, I managed to reproduce the issue and it looks like also to fix it. Please anyone who's able to test it, let me know if it's now working in sonarr.
It should be fixed in version 1.5.6
Closing as so far it seems to work fine for me. Please reopen if you have issues.
Works well for me, thanks!