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

Upgrade best practices?

A

Andrew Millne

Guest
I'm looking to update PHP 4.3.9 to 5.x and thought I may as well upgrade to Plesk 8.6 at the same time (Think I'll wait a few more point releases before jumping to 9).

I will be following the atomic turtle wiki to run the yum updates.

Should I run the plesk update first or the atomic turtle updates?

Also when updating Plesk is it a good idea to upgrade incrementally or is it safe to just jump to the required version?

Also I am not entirely sure how to create a full server backup in case the worst happens. The best backup solution I have been able to use so far has been via the plesk panel backing up each client seperately and then downloading through the browser is there an easier way? The backup option found in virtuozzo is not an option as no backup server is set up.

Thanks in advance

- Andy
 
Back
Top