• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue TLS 1.2 and 1.3 only

E42

New Pleskian
Server operating system version
Debian 11
Plesk version and microupdate number
Obsidian
Hello,
I followed the guide here https://support.plesk.com/hc/en-us/...able-TLS-protocol-versions-in-Plesk-for-Linux

But this command:
plesk bin server_pref -u -ssl-protocols 'TLSv1.2 TLSv1.3'
Does not seem enough.
A simple test with the tester on Qualys SSL Labs will give "B" rating and show TLS 1.0/1.1 ciphers. So my guess is that we should also explicitly set TLS 1.2/1.3 only ciphers. How can I found such an updated / tried-and-tested / approved list? Is the one in the article above correct for TLS 1.2/1.3?
 
I just found your question. If it is still open then it could help to look in Plesk-UI for websites/domains/your domain/ssl-certificates/serverconfiguration. Here you can choose an appropriate variant for TLS/ciphers provided by mozilla which comes together with relevant ciphers. If you do this be aware that the modern variant only provides TLSv1.3 but the variant intermediate provides both TLSv1.2 and 1.3 . Having done this you will proably get A or A+ with ssl-labs test depending on HSTS enabled or not..
This works in my case now seamless in Plesk-UI and I do not configure it any longer in the bash.
 
If you arent looking for a specific kind of setup. But just want to be compliant with the current best
practices for SSL configuration, following one of the 3 levels of configuration current defined in:

Mozilla SSL Configuration Generator

1679533958354.png

Modern: Services with clients that support TLS 1.3 and don't need backward compatibility
Intermediate: General-purpose servers with a variety of clients, recommended for almost all systems
Old: Compatible with a number of very old clients, and should be used only as a last resort

The most simple way to apply one of those 3 templates in a few clicks is using SSL It!
- Make sure it is installed and open the SSL It! extension settings
(Tools&Settings->Security->TLS versions and ciphers management-> click settings)

1679533918214.png

- Here you can enable Mozilla ciphers and sync them to apply it.

(In your case. AND if you are aiming for an A or A+ rating. Select intermediate)

1679534435692.png

1679534740530.png

I suggest you reboot the server after configuring.
 

Attachments

  • 1679534384914.png
    1679534384914.png
    45.6 KB · Views: 5
Back
Top