![]() ![]() The remote certificate is invalid according to the validation procedure. > : The SSL connection could not be established, see inner exception. DownloadClientUnavailableException: Unable to connect to SABnzbd, The SSL connection could not be established, see inner exception. 22:15:07.5|Error|Sabnzbd|Unable to connect to SABnzbd, The SSL connection could not be established, see inner exception. 22:15:07.1|Error|X509CertificateValidationService|Certificate validation for failed. Browser and Version (Only needed for UI issues).Platform Information (please complete the following information): Test was aborted due to an error: Unable to connect to SABnzbd, The SSL connection could not be established, see inner exception. If I take TLSV1_ALERT_UNKNOWN_CA litterally, Radarr is trying TLSv1? (Not TLSv1.2 or TLSv1.3) fill out API key and check SSL, click Test.Radarr -> Settings -> Download Client -> SABnzbd.SABnzbd gives a traceback ssl.SSLError: tlsv1 alert unknown ca (_ssl.c:2623) Logfile says Test was aborted due to an error: Unable to connect to SABnzbd, The SSL connection could not be established, see inner exception. The remote certificate is invalid according to the validation procedure.". Mind you there have been a few docker image updates for sabnzbd over the last few days so maybe they screwed/unscrewed the pooch.Radarr 3.: with SABnzbd over HTTPS (self signed) results in "inner exception. It only started from 0.88 with me and I did add the extra port and ssl but I think it’s luck that it has not failed again. One change I did make yesterday was to specify the port: 8080 and ssl: false even those are the defaults and don’t need to be configured.Īnyway, you might think it’s fixed but it seems to be an intermittent problem. If you look in th e.py file you will see that it only does that persistent notification prompt for the API key when config via the API in config yaml fails… so if that fails and you have disabled discovery then the sabnzbd sensor won’t work at all. I entered it and it creates a nf in the donfig directory… But then when I restarted again, it would also come up with the config error in the log again and prompt AGAIN for me to enter the API key even though the conf file exists. When mine started doing this a couple of days ago, it started prompting via the persistent notification for the API key. It might get rid of the annoying persistent notification but it won’t work either. ![]() If you disable discovery, then if it isn’t detected via config and there is a config error then it won’t work at all. Sometimes it works, sometimes it doesn’t and gives an error in the log. ![]()
0 Comments
Leave a Reply. |