Web interface crashing

[chaoticyeshua]

Hello,

I am running SABnzbd version 3.1.1 as a Windows service. Several times a day, I receive the below error and randomly my web interface quits working until the service is restarted. I have HTTPS enabled and am using a self-signed certificate. It is the same certificate I've been using for a couple of years with no issues - this problem recently started, within the last week or two. I am also using the same certificate with other services hosted on the same computer without any issues with those services. I have enabled debug logging, and the only other anomalies I see other than the below error are a lot of API calls coming from my router's IP address. I'm not sure what would cause that, other than that I do typically have SABnzbd exposed to the internet and it's possible bots are attempting access. The port is no longer being forwarded until I know what the API calls are. Any advice would be appreciated.

Error displayed:

Code: Select all

ssl.SSLError: [SSL: SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate (_ssl.c:2623) 

Examples of other concerning log entries (there are tons of these for the past day):

Code: Select all

2020-12-07 10:04:12,239::DEBUG::[apikey=<APIKEY>] API-call from 192.168.1.1 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36] {'mode': 'history', 'search': '', 'failed_only': '0', 'start': '0', 'limit': '20', 'last_history_update': '142', 'output': 'json', 'apikey':<APIKEY>', '_': '1607220902155'}
2020-12-07 10:04:13,257::DEBUG::[apikey=<APIKEY>] API-call from 192.168.1.1 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36] {'mode': 'queue', 'search': '', 'start': '0', 'limit': '20', 'output': 'json', 'apikey':<APIKEY>', '_': '1607220902156'}

[sander]

Do you use Radarr? If so, which version?
Do you use other *arr programs?

[chaoticyeshua]

Hi, thanks for the response. I use Sonarr, Radarr, and Bazarr. I noticed Radarr auto-updated to a newer version and was no longer functioning. I ended up having to reinstall the latest build and reset all my settings. I'm going to work on setting that back up again when I have some time (likely tomorrow). Is that the cause of this issue?

[sander]

I'm not sure: the newest version of Radarr causes another error in SAB, and eventually SAB stops responding.

[chaoticyeshua]

Just FYI, after reinstalling Radarr and setting it up again from scratch, I'm not getting this error anymore. I ended up having to use OpenSSL to convert my cert/key files into a pfx format certificate instead to enable https for Radarr (SSL certificates are done differently for it now), but it's working fine so far. Will let you know if the SABnzbd web interface crashes or displays the warning again.

[sander]

which cert/key files do you mean? Those generated and used by SABnzbd?

If so, please let me know how you did that, so that that I can try myself

[chaoticyeshua]

I had created my own self-signed certificate using OpenSSL several years ago. I can't remember the commands I used to generate it. I had the cert stored in a .cert file and the private key in a .key file as required by SABnzbd. I used OpenSSL, running this command, to merge them into a single .pfx file for use with Radarr:

openssl pkcs12 -export -out new_cert.pfx -inkey current_cert.key -in current_cert.cert

[sander]

to merge them into a single .pfx file for use with Radarr

Ah, yes ... you imported the self signed stuff into Radarr.

I thought (hoped) you had a solution on the SAB side.

Thanks.

[chaoticyeshua]

Well, what I'm saying is that so far I have not seen the issue with SAB arise again after fixing Radarr. I'll keep you in the loop though just in case it does.

[chaoticyeshua]

It's been almost a full 24 hours without a warning in the SAB interface, and without the SAB interface crashing. A full uninstall/reinstall of Radarr and setting it up again from scratch seems to have resolved the problem for me. I also did notice in Radarr in Settings > General > Security section there is an option called "Certificate Validation" -- its description is "Change how strict HTTPS certification validation is" and I set that to "Disabled for Local Addresses". I'm not sure if this helps with anything or not in regards to SAB connectivity, but I'm running the latest Radarr and no longer have any problems. Before, the web interface was displaying the warning mentioned in the first post on this thread about every hour and it was crashing about every 12 hours.

[sander]

Oh, wow, indeed ... with

in Radarr in Settings > General > Security -> "Certificate Validation" set to "Disabled for Local Addresses"

in Radarr 3.0.0 ... and no more tracebakcs on the SAB side!

That is good news for Radar 3.0.0 & SABnzbd users.

Thank you, @chaoticyeshua

Code: Select all

2020-12-09 16:25:49,649::DEBUG::[apikey=<APIKEY>] API-call from 127.0.0.1 [Radarr/3.0.0.4204 (windows 10.0.19041.0)] {'mode': 'version', 'apikey':<APIKEY>', 'output': 'json'}
2020-12-09 16:25:51,683::DEBUG::[apikey=<APIKEY>] API-call from 127.0.0.1 [Radarr/3.0.0.4204 (windows 10.0.19041.0)] {'mode': 'get_config', 'apikey':<APIKEY>', 'output': 'json'}
2020-12-09 16:25:53,713::DEBUG::[apikey=<APIKEY>] API-call from 127.0.0.1 [Radarr/3.0.0.4204 (windows 10.0.19041.0)] {'mode': 'get_config', 'apikey':<APIKEY>', 'output': 'json'}
2020-12-09 16:25:55,747::DEBUG::[apikey=<APIKEY>] API-call from 127.0.0.1 [Radarr/3.0.0.4204 (windows 10.0.19041.0)] {'mode': 'get_config', 'apikey':<APIKEY>', 'output': 'json'}
2020-12-09 16:25:57,785::DEBUG::[apikey=<APIKEY>] API-call from 127.0.0.1 [Radarr/3.0.0.4204 (windows 10.0.19041.0)] {'mode': 'version', 'apikey':<APIKEY>', 'output': 'json'}

[chaoticyeshua]

I'm glad to see that seems to have worked for you as well! Hopefully it helps others.

[chaoticyeshua]

Well perhaps I spoke too soon. A little while ago I received a different error (though still no crash so far):

Code: Select all

ssl.SSLError: [SSL: VERSION_TOO_LOW] version too low (_ssl.c:1124)

[sander]

API calls coming from my router's IP address. I'm not sure what would cause that, other than that I do typically have SABnzbd exposed to the internet and it's possible bots are attempting access. The port is no longer being forwarded until I know what the API calls are.

Is that port still closed?

[chaoticyeshua]

No, I opened it back up again.

I didn't realize the web interface uses API calls to collect data. The concerning log entries were likely me leaving the web interface open on another computer outside my network, or viewing from my phone. I had the refresh set to 1 sec, so that's why there were so many calls.