Indexers are unavailable and fail

[Traffiq]

Sonarr version (exact version): 3.0.10.1567
Mono version (if Sonarr is not running on Windows):
OS: Windows 11 Home Version 24H2
Debug logs: PrivateBin
Description of issue:
I have had 3 error messages for about a month
-All indexers are unavailable due to failures for more than 6 hours
-All search-capable indexers are temporarily unavailable due to recent indexer errors
-All rss-capable indexers are temporarily unavailable due to recent indexer errors

[fanboy]

Please upgrade to v4 first and then try again

[Traffiq]

Hello, I updated Sonarr to 4.0.15.2941 (newest I believe) and I am still having the same 3 issues in the status tab. Not sure if it’s worth mentioning but I am having the same issues on Radarr as well. (fully updated too)

[fanboy]

OK. Please turn off Trace logs (Debug is fine to start with)
Click Test on one (or all) of your Indexers - it should give you an immediate error and indication of what the issue is
Post those errors plus logs if you are unable to resolve yourself based on the above
Also make sure to try deleting and re-adding the Indexers in case something got messed up with the saved instances.
Check your APIs are correct etc.

[Traffiq]

Hello again, So I put on debug logs and tested the one Indexer I have set up, the error message is,
“Unable to connect to indexer, please check your DNS settings and ensure that IPv6 is working or disabled. No connection could be made because the target machine actively refused it. (127.0.0.1:9117).”

I am looking at the debug.txt file and there is a lot of text in there, would you like to see it all?

Once again, thank you for all the help

[fanboy]

OK, so does the indexer work in Jackett?
And just not connecting to Sonarr? Or does it not work in Jackett either?

I don’t use, so I’m not familiar, but from what I’ve read it might be worth trying Prowlarr instead, which is designed for easy integration with the *arrs

https://wiki.servarr.com/en/prowlarr
https://trash-guides.info/Prowlarr/

Otherwise there’s suggestions of using the direct IP instead of localhost for Jackett etc. You can search using the generated error to find all the other threads from people who have encountered the same and try the fixes suggested in those.

Or, if you only have one indexer, why not just add it directly?

[Traffiq]

When running a test in my indexer it fails with the above message. I had a friend of mine set this up for me, so I am trying to figure a bunch of this out myself, so sorry if I seem lost. Even though the name of the indexer is called Jackett the URL is set up with Torznab. Are you familiar with this?

[fanboy]

You seem lost, but you’ll get there. Perhaps at this point you should get your friend to explain and show you how this all works, since you are going to want to understand how it all links up, and how to troubleshoot and make changes. Since they set it up for you, it’s probably the fastest way to get you up to speed.

If you want to do it yourself then you’ll want to go consult and read the wikis/guides.

Jackett is a separate app; an indexer proxy/aggregator
It needs to be running and setup properly and working before it can be used in Sonarr
Since it is not working in Sonarr you need to check directly in Jackett first to confirm everything is working there. It will have it’s own URL ( http://localhost:9117 ) and interface that you can view and login to, similar to what you do with Sonarr.