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

New Server Migration

Jayson

Basic Pleskian
Hello All,

I have a new Centos 5.7 server to replace my old Centos 5.4. I installed Plesk 10.3.1 on the new one (trial license) and the old server has 9.3.0 (unlimited domain licensing). Both have the same php version 5.2.x and mysql versions 5.0.x.

I did a test migration of a user account with many domains and it seems to have worked correctly. Since this is my first migration manager use and the server also hosts mail and dns for everything I was hoping for a little direction. Is it best for me to just migrate the whole server and move the dns/email ip addresses to the new box after? I do this remotely, so I'm not sure if i just shutdown psa on the old server when I"m done, login to the new one add the ip addresses and keep going?

Thank you

Jay
 
Back
Top