• 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.

Question CentOS 7 and TLS1.3 with Let'sEncrypt. How is this possible ?

OverWolf

Regular Pleskian
Hi,

I'm on CentOS 7.9.2009 with openssl 1.0.2 and Plesk 18.0.39u1 with Let's Encrypt 2.13.7 and my websites have a connection encrypted with TLS 1.3. How is this is possible ? I know that I can setup and use TLS 1.3 with openssl 1.1.1k and more (for example with CentOs8).

Other question about chipers priority; I have seen that connection use for TLS 1.3 is TLS_AES_256 but I would like to change it with TLS_AES_128. How can I do it if I haven't configured any chipers for TLS 1.3 ?

Thank you in advance
 
TLSv1.3 for websites on CentOS 7 only works if you are using nginx for your websites. The nginx version that comes with Plesk is compiled against OpenSSL 1.1.1 and has TLSv1.3 support, while Apache httpd is provided by the OS vendor (Redhat/CentOS) and has no TLSv1.3 support.

Regarding ciphers: Have a look here:
 
Hi Monty,

thank you very much for your support.
For ciphers, can I configure them only with plesk bin server_pref ? So is ssl.conf in /etc/nginx/conf.d/ useless ?
 
Back
Top