• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

TLS connect failed

G

Garry Howard

Guest
I'm getting this error message for a lot of subscribers to a mailman mailing list:

TLS connect failed: error:24064064:random number generator:SSLEAY_RAND_BYTES:pRNG not seeded; connected to 67.18.94.18.
I'm not going to try again; this message has been in the queue too long.

It doesn't happen for all subscribers, but for a rather large number. It seems to have something to do with openssl. I have scoured the Internet looking for a solution to this problem but so far haven't found an answer. Any ideas?

Garry
 
You must log in or register to reply here.

Similar threads

A
Issue FTP - Insecure server, it does not support FTP over TLS.
Replies
3
Views
750
Alban Staehli
A
K
Resolved Plesk panel update fails with "certificate has expired"
Replies
3
Views
643
Sebahat.hadzhi
Sebahat.hadzhi
Polli
Issue Mails only possible with a wildcard certificate
Replies
5
Views
629
Polli
Polli
M
Issue Mail issue: Remote server returned '554 5.7.4 < # 5.7.4 SMTP; 554 5.7.4 failed to deliver message via SSL/TLS. >' -lost connection after STARTTLS from
Replies
1
Views
859
scsa20
scsa20
W
Question How to Prevent High Connection Counts Causing High Memory Usage (Possible DDoS?)
Replies
7
Views
2K
Bitpalast
Bitpalast
Back
Top