• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Client does not exist, but is expected to

D

dennis00

Guest
This isg like the 3rd time I have this issue with one of my servers. I currently manage 20 Plesk webhosting servers.

This is the third time I am facing this issue, and it was three times on a different server. Unfortuneatly the last time was more than half a year ago and my memory doesn't reach that far.

I am trying to transfer a domain on a dedicated server from a client of mine to a reseller account on a different Plesk-server. I can perfectly select the domains(4) I wish to migrate. It will backup the files and send them to the other server. Yet while restoring or after restoring it gives the message "Client xxx does not exist, but is expected to".

The issue seems to be related to the source server, as moving any domain to a different server using the migration manager gives issues. No matter which domain I select on the source server and no matter which client I select on the other server. Issues remain.

Does anybody have these experiences and was able to solve this issue?
 
Hi,

try to update Plesk on destination node to latest one. Also, look in migration.log in /usr/local/psa/PMM/var for more information. There should be some useful clues. If neither of this help -- yell support ;)
 
Back
Top