TLS certificate verification failed for nntp.ovpn.to: unable to get issuer certificate.

Get help, report and discuss bugs.
Post Reply
kiesel
Posts: 7
Joined: 06 Sep 2015, 17:12

TLS certificate verification failed for nntp.ovpn.to: unable to get issuer certificate.

Post by kiesel » 14 Apr 2019, 13:43

Hi,

I followed the link in the error message and added the new .pem file, but I am still getting the same error.

I am also not sure whether this applies in my situation because the error message is different?

Any ideas?

Thanks!


sanderj
Posts: 111
Joined: 10 Feb 2014, 21:46

Re: TLS certificate verification failed for nntp.ovpn.to: unable to get issuer certificate.

Post by sanderj » 15 Apr 2019, 17:42

kiesel, out of curiosity: how do you connect to nntp.ovpn.to
I assume with nntps / secured NNTP (not NNTP or HTTP or HTTPS)?
And over Internet, or from within a oVPN VPN?

Because:
https://www.sslshopper.com/ssl-checker. ... vpn.to:563 tells there is no valid SSL/TLS on the NNTPS port 563

And https://vcp.ovpn.to/?site=news tells a lot of difficult things / constraints:
Please update your Stunnel config: download CAfile and put into stunnel.conf folder

oVPN Users will get best results with internal DNS: 172.16.32.1 (or static hosts-file entry "172.16.32.1 nntp.ovpn.to")
Our internal DNS will send you directly from your connected oVPN server to our nntp endpoints!
SSH Users should use local forwarded port "-L 1563:172.16.32.1:1563" and add a entry to hosts-file: "127.0.0.1 nntp.ovpn.to" to prevent SSL certificate warnings.
If you use our usenet without SSH or VPN: you can use any oVPN.to Server IP as a static hosts-file entry for "nntp.ovpn.to".
IMHO that looks like nasty setup, not for the faint of heart.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 2 guests