SAB stopped checking RSS feeds

[MiG]

I have two very similarly configured instances of SAB running, one is a Win7 desktop for the heavy lifting and the other is a Raspberry Pi which monitors my RSS feeds while the main machine is offline. Both use the same indexer and have been operating in this configuration for years, however for some reason the RasPi has stopped pulling in NZBs a couple of days ago, even though the Win7 machine works just fine.

The RasPi is connected to the web and able to ping places, available space is sufficient for pulling in the nzbs (9.6GB) and at the bottom of the RSS feed URL pages NZBs appear. I've tried restarting SAB and a full reboot, to no avail. Any idea what could be going wrong here?

[safihre]

Could you enable Debug logging in the Status and Interface settings window. Then restart SABnzbd, and when you expect the readout to happen again, click Show Logging and check if there's anything in the log about the RSS readout.

[MiG]

Thanks! There's an SSL issue apparently:

Code: Select all

2019-11-15 07:23:33,382::INFO::[rss:309] Failed to retrieve RSS from (INDEXER): <urlopen error [Errno 1] _ssl.c:504: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure>

The RPi has not received any updates recently, and the exact same URL works fine on the Win7 machine. Any idea what could suddenly cause this?

[safihre]

Seems like a problem with SSL, can you double check the URL and if a browser or curl on the Pi can actually open the URL's?
Maybe they should be http instead of https?

[sander]

Thanks! There's an SSL issue apparently:

Code: Select all

2019-11-15 07:23:33,382::INFO::[rss:309] Failed to retrieve RSS from (INDEXER): <urlopen error [Errno 1] _ssl.c:504: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure>

The RPi has not received any updates recently, and the exact same URL works fine on the Win7 machine. Any idea what could suddenly cause this?

If you tell us the RSS Indexer's URL, we can help further. No need for password or other details.

A possible cause could be: the indexer has changed it's certificate of which your Raspi does not know / not trust the root certificate.

But we can only tell if you provide the URL / FQDN, so https://blabla.myindexerxyz.com/ ...