Getting untrusted certificate with some of my usenet servers

[jello]

Getting this: Server news dot eweka dot nl uses an untrusted certificate [Certificate not valid. This is most probably a server issue.] on some of my servers and and others are connecting just fine. when i try and connect without ssl, i connect fine to the server. this is happening with eweka, tweaknews, and newsgroupdirect. i am on windows 11 with sab 4.03

[sander]

https://www.appelboor.com/cgi-bin/check ... s.eweka.nl tells eweka is correct. So the server side is OK.

As you're on Windows, the most probably cause is a windows virus scanner is causing this.

[jello]

sorry its windows 10, all i have is windows defender activated and i deactivated it to see if i solved any issues, but i am still having the same errors after turning off windows defender...

[safihre]

Have you done all your Windows updates and restarted?

[jello]

Have you done all your Windows updates and restarted?

Yes.

[jello]

i tried my servers with nzbget and they all worked except for eweka which i had to change to ipv4 instead of auto then it worked with ssl...

[sander]

In SABnzbd, what newsserver do you use for eweka?

[jello]

news.eweka.nl

[sander]

OK, news.eweka.nl is good.

AFAIK nzbget brings its own certifactes and doesn't use the Windows certificates. If so, that is the explanation news.eweka.nl is OK for nzbget. Or: you have allow nzget to bypass the virusscanner / firewall.

Anyway, back to SABnzbd: if you can't solve it (in Windows, or your firewall/virusscanner), you can turn off certificate checking in SABnzbd:

SABnzbd -> Config -> Server. In the upper right corner, set Advanced Settings to On
Then click on the server settings of eweka, and go to Certificate verification, and set to Disabled. Then click Save.

[sander]

PS:

Out of curiosity: what happens if you open https://news.eweka.nl/ in Edge and in Chrome. You must wait 5-10 minutes before results appear.

In Chrome, I get the below, which is good: a secure connection is possible.

Code: Select all

200 Welcome to Eweka
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*

[jello]

PS:

Out of curiosity: what happens if you open https://news.eweka.nl/ in Edge and in Chrome. You must wait 5-10 minutes before results appear.

In Chrome, I get the below, which is good: a secure connection is possible.

Code: Select all

200 Welcome to Eweka
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*
480 Authentication Required*

i got the same results

[jello]

OK, news.eweka.nl is good.

AFAIK nzbget brings its own certifactes and doesn't use the Windows certificates. If so, that is the explanation news.eweka.nl is OK for nzbget. Or: you have allow nzget to bypass the virusscanner / firewall.

Anyway, back to SABnzbd: if you can't solve it (in Windows, or your firewall/virusscanner), you can turn off certificate checking in SABnzbd:

SABnzbd -> Config -> Server. In the upper right corner, set Advanced Settings to On
Then click on the server settings of eweka, and go to Certificate verification, and set to Disabled. Then click Save.

both nzbget and sabnzbd were already allowed in my firewall. its not just doing it with eweka, but also newsgroupdirect and now doing the same thing with nzbget too, is it safe to turn off verification?

[sander]

is it safe to turn off verification?

It's less safe than having it on. Reason: SSL is there to guarantuee end-to-end encryption and verification. If that check fails, it the sign that that is not working.