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

[Bug] Plesk replaced Private Key for SSL Certificate

fragger1991

New Pleskian
Hello,

we have migrate our existing Plesk 12.0.18 (Debian 6.0.10) to an new Server with Plesk 12.5.30 (Debian 8.2.0). I used the Migration Manager for copy the Files for Web, Mail and DB Content.

We want to use our existing SSL Certificate for our Domain, which is qualified by Comodo - when i add an Certificate and want to use our existing Private, Cert and CA Keys then Plesk will replaced the private Key. I have merged the Keys, they doesn't match.

So i have copied the Key to /opt/psa/admin/conf/httpsd.pem directly and restart the Engine (/etc/init.d/sw-engine restart) - after i do this, all is okay and we can use the Certificate with Plesk without any issues. But this appears by "Domain only" too, so if i update the Keys in the Database (DB: psa, Table: certificates) and update the File under "/opt/psa/var/certificates" manually, all is work.

So i think this is a Bug.

Kind Regards
 
Back
Top