• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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
473
frame86
F
M
Question Are Plesk servers susceptible to TLS BREACH attacks? (cve-2013-3587)
Replies
1
Views
791
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