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

Full server migration to new server with same hostname?

Chris1

Regular Pleskian
Hello,

I'm wondering whether it is possible to perform a full server migration to a new Plesk server with the same hostname or will Plesk give an error about the hostname being the same?

The new server would not be accessible by hostname (only via IP) until DNS and glue records were changed after the migration.

Would there be any problems with this?

Kind regards,
Chris
 
I think that there are shouldn't be problems with migration if this hostname is not resolvable on destination server. You can try at least.
But why you can't change hostname to production after successful migration?
 
Back
Top