SABnzbd Forums

I have been out of town for a few days and when I came back and checked my server, I was missing a bunch of show episodes. When I checked SAB, I had two pages of:

2017-01-25 13:58:29,408::INFO::[newswrapper:290] Failed to connect: Server news.supernews.com uses an untrusted certificate [[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)] 29@news.supernews.com:563

Nothing has changed and I have been using the same servers for the past two years. The only way I have been able to resume my downloads is by disabling the certificate verification.

On https://www.appelboor.com/newsservers/n ... h-SSL.html you'l see news.supernews.com is ... TRUSTED.
My own SABnzbd also trusted supernews.

So the problem is on your side (or in the middle: your ISP). On what operating system (and hardware if NAS) is your SABnzbd running?

Windows Server 2012 R2. Os is on it's own drive with all the apps (SAB, SB etc.) and the storage is on a 16TB raid 6 behind an adaptec 3805.

MeatPopsicle wrote:Windows Server 2012 R2. Os is on it's own drive with all the apps (SAB, SB etc.) and the storage is on a 16TB raid 6 behind an adaptec 3805.

Would you like to analyse it (which will take time), or are you OK with the non-checking?

Analysis could involve:
* does it still happen?
* does it happen on another system in your house running SABnzbd (Windows PC, or ...)
* what brand is the Windows Server hardware? Lenovo, ... ?
* what virusscanner , firewall and other security software is installed on the Windows Server
* what if you run wget on the Windows Server like this "wget https://news.supernews.com:563/" ?
* what if you run curl on the Windows Server like this "curl https://news.supernews.com:563/" ?

I have done a little more testing.

I installed SAB on my pc, went through the wizard and used the test connection button and news.supernews.com worked.

With that in mind I started testing on my server.

I am using news.supernews.com, news.eu.supernews.com, ssl-us.astraweb.com and ssl-eu.astraweb.com as priority 0-4 respectively. All of them are giving the untrusted certificate error.

Is there a cache or something that I can clear? Maybe something got corrupted?

You have now answered my question 1
.
Now answer question 2 - 6 .. :-)

Actually, that was 1 and 2. =D

what brand is the Windows Server hardware? Lenovo, ... ? - Custom build Intel Xenon proc, Supermicro mobo, Crucial ECC RAM, pretty standard hardware that has been running SAB for two years with no issues

* what virusscanner / firewall is installed on the Windows Server - none

* what if you run wget on the Windows Server like this "wget https://news.supernews.com:563/ " ? - I tried running this is powershell and got:

wget : The server committed a protocol violation. Section=ResponseStatusLine
At line:1 char:1
+ wget https://news.supernews.com:563/
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
eption
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

* what if you run curl on the Windows Server like this "curl https://news.supernews.com:563/ " ? - got the same above error

No Lenovo, so no built-in spyware. Good.

No virusscanner: good.

I'm not sure about the wget/curl/powershell error message: does that confirm the problem SAB also experiences (no secure connection to news.supernews.com), or is a program error?
What happens when you do "curl https://www.google.com/"

Additional, bonus question: what if you fill out "newsreader.eweka.nl" with SSL in SABnzbd, and click on Test Server?

curl https://www.google.com/ - gave me a internet Explorer security pop-up

what if you fill out "newsreader.eweka.nl" with SSL in SABnzbd, and click on Test Server? - says it requires a username and password

So I signed up for a giganews trial account just for SnG's, put in the server and credentials and it works with ssl. I then reset all the other servers to default and saved the changes and tested them and they all now work with SSL again. Wierd. Thanks for all the help though. =D

Strange. But good that it works now.