Unable to connect to indexer nzb.su SSL error

Help & Support
#1

Sonarr version (exact version): 3.0.6.1342
Mono version (if Sonarr is not running on Windows): 5.20.1.34
OS: Synology NAS
Debug logs: https://pastebin.com/nsDw705X
Description of issue:
The indexer nzb.su is throwing an SSL error and won’t connect. Other indexers such as nzbfinder and usenet-crawler work fine.

the error seems is: (full log above in pastebin)

-- : Unable to connect to indexer, check the log for more details
2021-10-11 12:39:49.4|Error|X509CertificateValidationService|Certificate validation for https://nzb.su/api?t=caps&apikey=(removed) failed. RemoteCertificateChainErrors
2021-10-11 12:39:52.0|Error|X509CertificateValidationService|Certificate validation for https://nzb.su/api?t=caps&apikey=(removed) failed. RemoteCertificateChainErrors
2021-10-11 12:39:52.1|Warn|Newznab|Unable to connect to indexer
1 Like
#2

I have the identical problem, with nzb.su, and some other indexers (but not all my indexers). I am using Synology NAS with mono, version numbers identical to OP, and error logs comparable to OP.

#3

That sounds like it’s due to the Let’s Encrypt Root Cert expiring perhaps. Take a look at this thread which has some decent info https://www.reddit.com/r/usenet/comments/pyo27t/ndngd_lets_encrypt_root_certificate_expiration

#4

Same here… Exact same software version for Sonarr and Mono as OP.

Sonarr version (exact version) : 3.0.6.1342
Mono version (Running on Syno) : 5.20.1.34-16
OS : Synology NAS ( Version: 6.2.4-25556 Update 2 )

Logs are exactly the same as OP, this also happens while trying to connect to NZB.su

#5

go to Settings > General and change Certificate Validation to Disabled and it will then start working

only fix i could find

#6

Thx. unfortunately I cannot confirm this workarround.

I managed to get my system up and running by;

  • taking backup from Sonarr.
  • Remove Sonarr from Synology
  • Remove Mono from Synology
  • Reboot Synology NAS.
  • Reinstall Sonarr in Synlogy ( this will also install Mono)
  • After installation, go to Sonarr Gui and update the Sonarr to 3.0.6.1342
  • After upgrade, restore the backup.

After these steps I was able to configure nzb.su as an indexer again.

#7

This is insecure and not a valid solution

#8

I don’t think you need Https option turned on…

  • If your download client and Sonarr are on the same machine there is no reason to use HTTPS, so the easiest solution is to disable SSL for the connection. Most would agree it’s not required on a local network either. It is possible to disable certificate validation in advanced settings if you want to keep an insecure SSL setup.

https://wiki.servarr.com/sonarr/faq

#9

the faq entry is in regards to accessing SSL in sonarr or connecting to download clients via SSL; it has nothing to do with indexers and you should not disable SSL cert validation for indexer issues…given it’s easily fixable and thousands of others have solved in since this has begun occurring at the end of sept with the LE cert expiration.

#10

likely either inadvertently upgraded mono / updated mono’s cert store / or upgraded sonarr (or a combo of those)

either way this would be the solution - not the insecure answer marked as a ‘solution’

1 Like
#11

I also have the same/similar issue. No https indexer or downloader connections work. Disable certificate validation does not fix this issue. It used to work many months ago and does work in radarr/lidarr when disabling certificate validation. I am using the linuxserver docker on a Synology NAS, sonarr version 3.0.6.1342, mono version 5.20.1.34. Not a huge issue but after several months I decided to see if anyone else was having the problem.

#12

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