• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Problem with STARTTLS - SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:.\ssl\s2

J

jcalegre

Guest
RESOLVED: Problem with STARTTLS - SSL routines:SSL23_GET_SERVER_HELLO:unknown pr

Hi,

I've some problems connecting to my mailserver using STARTTLS.

I've done a simple test:
openssl s_client -starttls smtp -crlf -connect my.domain.com:25
Loading 'screen' into random state - done
CONNECTED(00000768)
11128:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:.\ssl\s23_clnt.c:583:

Weird, because i should receive something like:
CONNECTED(00000768)
depth=0 /C=US/ST=Unknown/L=Unknown/O=Unknown/... etc?
right?

I've a "self made" servercert.pem at /var/qmail/control/

What whould i do to resolve this problem?

Tx,

Jcalegre
 
I've copyed my psa certfile from (/usr/local/psa/var/certificates/) to servercert2.pem (/var/qmail/control/) and then:

$ cp servercert2.pem servercert.pem
..changed the owners/groups...
$ chown root:nofiles servercert.pem
$ chmod 640 servercert.pem

$ cp servercert.pem clientcert.pem
..changed the owners/groups...
$ chown root:qmail clientcert.pem
$ chmod 640 clientcert.pem

working now..

I hope!
 
Back
Top