'Unable to start SSL' errors suddenly (6.91 RC3 Build 5585)?
Posted: Wed Oct 09, 2024 5:55 pm
Background:
I have been using Newsbin for a long time without any server connection issues.
I have also been using this new 6.91 RC3 Build 5855 version without issues for a little while.
Issue:
Yesterday suddenly I started getting SSL errors constantly.
Error message in Newsbin Pro:
ERROR (News Server name masked)SSL Lib returned error: 0xffffffffffffdaa0
ERROR Downloader: Socket Exception NEWS SERVER ERROR Unable to start SSL to news server Error: SSL Negotiation Failed, Host: (News Server name masked)
Some of the steps tried to resolve the issue so far without success:
1) Rebooted PC
2) I have tried disabling my internet security software firewall and real-time protection.
3) I reinstalled Newsbin Pro (however did NOT let it delete settings files NOR delete the registry settings though).
4) Checked that the usenet provider's certificate is valid (on their end at least).
Any suggestions would be much appreciated!
Any certs to check on my end?
Going to try to replicate the issue on a different computer when I get a chance.
I have been using Newsbin for a long time without any server connection issues.
I have also been using this new 6.91 RC3 Build 5855 version without issues for a little while.
Issue:
Yesterday suddenly I started getting SSL errors constantly.
Error message in Newsbin Pro:
ERROR (News Server name masked)SSL Lib returned error: 0xffffffffffffdaa0
ERROR Downloader: Socket Exception NEWS SERVER ERROR Unable to start SSL to news server Error: SSL Negotiation Failed, Host: (News Server name masked)
Some of the steps tried to resolve the issue so far without success:
1) Rebooted PC
2) I have tried disabling my internet security software firewall and real-time protection.
3) I reinstalled Newsbin Pro (however did NOT let it delete settings files NOR delete the registry settings though).
4) Checked that the usenet provider's certificate is valid (on their end at least).
Any suggestions would be much appreciated!
Any certs to check on my end?
Going to try to replicate the issue on a different computer when I get a chance.