• 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 from 7.5?

J

jplotzke

Guest
Hello all,

I'm thinking of upgrading my Plesk 7.5 installation directly to 8.2.1. I know there were some scary issues to the upgrade of 8.0. Have these been resolved? Is it safe to take the plunge? Any suggestions?

Thanks!

~Jeff
 
Hi

Make sure the latest release exist for your OS:
ftp://download1.swsoft.com/Plesk/Plesk8.2
Also it's better to upgrade using the latest autoinstaller taken for example from ftp://download1.swsoft.com/Plesk/Plesk8.2/<os version>psa_installer_v3.2.1_.....

Many errors were fixed there.

Plesk upgrade used to fail when the Plesk password contained : or #. But it should be fixed in the latest autoinstaller. It's just for your information.

See also the following known issues:
http://kb.swsoft.com/en/2013
http://kb.swsoft.com/en/2201

Also it's better to upgrade first the 7.5.4 with all the packages available for this version. Then you can try to upgrade up to the latest version.
Anyway, the backup is highly recommended, make it with backup agent from 8 version, like it's described here:
http://kb.swsoft.com/en/1727

Plesk doesn't allow to restore backup made on minor versions to the later version. That's why if you make the backup with the backup agent of Plesk 8, you'll have the possibility to restore everythying.
 
Back
Top