• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Unable to assign ssl certificate to plesk server

I am in the same situation. RapidSSL from GeoTrust. Created in Server>Certificates, assigned it to all 3 IPs on the machine (shared IP and two unused dedicated), checked the box and clicked "Use the selected certificate to secure connections to control panel" ... even restarted bind and apache ... completely shut down bind and apache, then started them again ... went as far as to restart the whole VPS I am on.

I then uploaded the Cert/Ca to may domain to see what would happen. If I access https://www.mydomain.com everything is proper. But, If I access https://www.mydomain.com:8443 Plesk is still using its default (untrusted) self-signed cert.

Any ideas why it won't work with the Control Panel?

Edit: Just realized This was a post in the 8.4 forum ... I am using a Virtuozzo based VPS with PSA 8.6 (100 domain license)
 
Back
Top