Facebook
Twitter-
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.
Error migrating to Plesk 12.5
- Thread starter vcentos
- Start date
Hello! Looks like you have an issue with decoding of passwords on your source Plesk server. That's why XML dump of your source become broken (non-unicode characters was placed instead of passwords after decoding). We will try to fix such issues in future Plesk Migrator releases, but for now I suggest you to find "broken" password and reset it on source. After that migration could be continued.
To find "broken" passwords you need to extract XML dump(s) from archive (/usr/local/psa/var/modules/panel-migrator/sessions/20160525211102/plesk.backup.source.raw.tar) and validate it using any XML validator. I can do it for you if you send me noted file via private conversation (it will contain sensitive data, like passwords etc.).
To find "broken" passwords you need to extract XML dump(s) from archive (/usr/local/psa/var/modules/panel-migrator/sessions/20160525211102/plesk.backup.source.raw.tar) and validate it using any XML validator. I can do it for you if you send me noted file via private conversation (it will contain sensitive data, like passwords etc.).
Similar threads
