- Plesk for Windows
An attempt to install DotNetNuke application under Plesk > Subscriptions > example.com > Applications > All Available Applications fails with:
PLESK_ERROR: Installation of DotNetNuke at http://example.com/ failed. Non-zero exit status returned by script. Output stream: 'Error during MSSQL version checking
[DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.
at (SiteApplicationManager::fsaExecuteScript line 458)
at execute console command --run-application-script(vconsoleapp::start line 122)
at execute "C:\Program Files (x86)\Plesk\admin\bin\sappmng" --run-application-script ...
SSL 3.0 and TLS 1.0 protocols are disabled on the server. This can be checked with this article.
This is Plesk bug with ID PPPM-9328, which is planned to be fixed in one of the future product updates.
Until the bug is fixed, use the following workaround:
Connect to the server via RDP
Enable SSL 3.0 and/or TLS 1.0 on the server following the instructions on how to manage SSL/TLS ciphers and protocols in Plesk for Windows?
Note: Even though the workaround exists, these protocols are considered as weak and their use is not recommended.
Please sign in to leave a comment.