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

Migration troubles

D

Decius

Guest
Hi there,

I'm starting a migration and up to this point it still has not asked me for the target server IP or anything. After I chose to migrate all data and all users on the next page I see the following error:

Migration cannot continue: either the selected objects are already migrated or they cannot be migrated because domain name or user account name is invalid.

Any clues?
 
Oops. I think I understand. The migration starts from the target, not from the source.

Might have to try it again on the target!

:)
 
Okay, here's a "ridiculous" issue that I don't fully understand - does Plesk expect that every person backing up their server will have enough space to have another entire copy of it on the same server?

I am trying the migration and my entire disk is full, so I'm going to have to cancel it and do it another way.

Ridiculous? You bet! (If I missed something and there's a work around, I humbly stand corrected)
 
Back
Top