• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue SSL_ERROR_RX_RECORD_TOO_LONG

Sysop

Sysop

Basic Pleskian
I mysteriously get the following error on CentOS 7, Plesk Onyx, Version 17.5.3 Update #34
Code: 
Secure Connection Failed

An error occurred during a connection to example.com:5858. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG

I have Let's Encrypt Certificate installed on the domain and the port is open in the firewall (5858 tcp). I've tried the following "solution", although it did nothing to solve my issue. Would anyone know what the issue is or how to fix it please?
 
You must log in or register to reply here.

Similar threads

B
Resolved domain uses plesk ssl certificate
Replies
2
Views
3K
biaaas
B
S
Issue Mail Server Certificate Conflict Despite Correct Assignment (SNI Error)
Replies
3
Views
4K
Martin Dias
Martin Dias
M
Issue Plesk showing Cloudflare Origin CA cert, but server still serving Google Trust cert
Replies
3
Views
10K
mauricekindermann
M
B
Issue Unable to issue a Let's Encrypt certificate for domain with forwarding hosting type: nginx is not installed or is disabled on the Plesk server
Replies
1
Views
3K
Sebahat.hadzhi
Sebahat.hadzhi
I
Resolved Preventing bot brute force probes against Postfix/SMTP
Replies
5
Views
2K
iainh
I
Back
Top