Indexer failing to connect

Sonarr version (exact version): 2.0.0.5338
OS: Windows 10 1909 - fully patched
I have 2 indexers running on Sonarr. DogNZB and NZBGeek. DogNZB test and runs just fine, but NZBGeek fails with some TLS version issues.

I’ve seen others say that updating windows to patch .NET solved some issues. Windows 10 finished fully patching and after a reboot, still get the same errors. Debug logs are attached: https://pastebin.com/2y26jhtj

I’m also curious about an initial error during the startup of sonar. It reads:
SecurityProtocolPolicy: Disabled TLS 1.2 due to remote certificate error. Not sure if that is just relating to the local certificate or something to do with the certificate connecting to the indexer?

Please post a link to the full ((debug log)) with that included, that may be the issue, but knowing when it

Apologies for not including those right away.

I went ahead and cleared the log. Then restarted Sonarr and then re-ran the test connection. Here is the debug: https://pastebin.com/abQ2PnCF

Attempted to reinstall sonarr this morning. NZBgeek still fails to connect.

If you disable SABnzbd and restart Sonarr does the test still fail? It looks like that is the reason TLS 1.2 is disabled, you’ll want to use HTTP or fix the cert if that’s the case

I regenerated the cert on SABnzb and that ended up fixing the issue.

1 Like

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