• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Migrate error at one subscription / domain

Maxwell Banks

New Pleskian
Server operating system version
Almaliniux 8
Plesk version and microupdate number
18.0.55 Update #2
Hi!
I have an account migrated yesterday with error (but ok email and db's) from the same plesk version to other server.
Today try to remove the task from migration, and make a big mistake, delete the migration from target.....

So I try to recreate the migration and when try to migrate receive the next error:

Failed to deploy subscription xxxx.com
Migration for that subscription is considered completely failed. No further actions are performed for it.
Migration tools tried to perform operation in 3 attempts: 'username'

My plesk is 18.0.55 and run from linux almalinux 8

Thanks!
 
There are probably leftovers such as system user accounts on the system so that a new migration cannot create these accounts. You must make sure that no user accounts that are part of the migrated content exist on the target server.
 
Back
Top