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

SSL certificates....

S

starchild2012

Guest
Hi,

We are about to embark upon a migration from plesk to plesk.

Last time we did it, the ssl certificates did not come across.

Will the ip's and ssl certificates mapped to those ip's all come across?

Is there anything that wont be migrated (assuming we choose all options), and that we will need to manually set up?

The plesk to plesk move is within the same hosting company BTW.

Thank you.
 
If you have a shared database server then its possible that the databases and the installed application vault apps using those databases wont be transfered over - however they will still be there and work, just not show up in the list of DBs/installed apps

For the SSL Certs its been fairly hit and miss for me, Ive seen it work beautifully, and some times I had to go through and click a couple buttons to finish the install (set the domain to use the new cert instead of the shared one, etc)

But in worst case you can always export the certs and then re-import them if you dont have a lot of them.
 
Thanks. We would have around 50 certs to do.

Last time we did this, I had to manually copy and paste the certificates over. An absolute nightmare.

Though it could have because we changed hsotsm, and could not migrate the ssl certificates.
 
Back
Top