• 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 issue with SSL connection to one domain

Andi

New Pleskian
Hi,

I have 3 domains hosted on my server where 2 domains work perfectly fine with SSL.

but one domain has issues. In a browser the SSL connection is verified and everything seems ok. But curl seems to have a problem

when I do: "curl https://domain.com" on commandline I get

Code:
curl: (35) SSL received a record that exceeded the maximum permissible length.

but when I do "curl https://www.domain.com" I get the 301 that is set up...

Plesk is configured to have "domain.com" as preferred setting

Code:
# openssl s_client -connect domain.com:443 -servername domain.com -debug
CONNECTED(00000003)
write to 0x1214940 [0x1253240] (265 bytes => 265 (0x109))
[...]
read from 0x1214940 [0x12587a0] (7 bytes => 7 (0x7))
0000 - 48 54 54 50 2f 31 2e                              HTTP/1.
139709845075872:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:769:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 7 bytes and written 265 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
---

when I do the previous with a leading "www." I get of course the correct cert output

all 3 domains are configured the same way... the only difference: the domain with the issue has subdomains, the others not.

the hostname was this domain but I changed it back to the hostname of my hoster... but this way my mail server gets problems with the others...

I also did a tcpdump... curl seems to connect to localhost (127.0.0.1) and gets a bad http response (400)

anyone got an idea what I can try?
 
Back
Top