• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Migration visual glitch -- duplicate errors when gathering client/domain list

websavers

Regular Pleskian
The attached image highlights the problem. It's a very minor visual glitch.

migration-retrieving-list-of-clients-domains.png

Steps to reproduce:

  1. Set up a migration from another server to this one
  2. While the migration manager is gathering the source server's object list, click somewhere else in the panel
  3. Navigate back to the migration manager and click on the migration task
  4. If the destination server hasn't yet gathered the full list of objects from the source server you get two duplicate errors like in the attached image

If you then wait long enough you can get into the migration task and proceed from there -- everything works fine at that point.

It is likely that this cannot be reproduced unless the source server hosts a large number of clients/domains.
 
The most possible cause of this error is the issue described in the following article: http://kb.parallels.com/120195
Also it can be related to limited license installed on destination server.
Check it at least.
 
Igor,

It's not the error I'm reporting here... the error is exactly correct. I haven't waited long enough for the Migration Manager to retrieve the list of objects on the source server.

The objective of posting this is to inform the Plesk devs that the error is duplicated unnecessarily.

I suppose it could also handle the error a bit better, but that's a whole other topic of discussion.

-Jordan
 
Back
Top