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

Enabling Plesk for TLS 1.1+

N

Nick Bradley

New Pleskian
PCI tests are now recommending to have TLS 1.0 disabled - it appears that Plesk doesn't support TLS 1.1 and higher by default.

Is there a way to enable support for TLS 1.1, 1.2, etc in Plesk? If it is enabled/supported - how do I get Plesk to recognize that TLS 1.0 is disabled and use the higher protocol? I found a KB that looks like a workaround for the Linux based Plesk, but not Windows.
 
You must log in or register to reply here.

Similar threads

F
Issue Can't add older database remote server
Replies
0
Views
375
frame86
F
M
Question Are Plesk servers susceptible to TLS BREACH attacks? (cve-2013-3587)
Replies
1
Views
661
scsa20
scsa20
M
Input Access issues with outdated Plesk Knowledge Base articles
Replies
1
Views
3K
Sebahat.hadzhi
Sebahat.hadzhi
Daerik
Issue Error Upgrading Plesk Obsidian 18.0.63 to 18.0.64: HTTPS Error 404 - Not Found (MaxScale Repo)
Replies
6
Views
3K
Daerik
Daerik
K
Question modsecurity
Replies
2
Views
1K
Knutsford
K
Back
Top