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

Maintenance & Cleanup

C

cmturner2

Guest
I was wondering if there is a set of best practices or details on cleanup post upgrade? In my case I'm at 8.6.0 but I started back at 8.2.

Specifically:

Which old paths can be purged (if any)?
e.g. .../psa/PSA_8.4.0/... ??
e.g. .../swsoft/PSA_8.2.0/... ??

And additional areas that should be cleaned up?

Is this documented somewhere I missed?

This isn't critical, not a space shortage or anything, I just like to keep things tidy.
 
You can remove those PSA_* directories. They contain the rpms downloaded by Plesk Updater/autoinstaller. You can even remove them for your current version as they're already installed. The rpms are not automatically removed after installation. It's sometimes handy to have them around when you want to reinstall some Plesk packages, but Plesk Updater/autoinstaller can always download them again.
 
Back
Top