• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Resolved Plesk Migration Extension Fails with List Object Error

technabob

New Pleskian
I'm attempting to migrate several websites (all under a single subscription) from one Plesk server (Both running Onyx 17.5.3) to another using the Migration Extension (version 2.10.10-0).

However, every time I attempt to run the migration, I get the following error:

Error: Plesk Migrator returned non-zero exit code COMMAND: '/usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator' 'add-task' '/usr/local/psa/var/modules/panel-migrator/sessions/20170722154640/config.ini' '--command-file' '/usr/local/psa/var/modules/panel-migrator/sessions/20170722154640/new-task-command.json' '--migration-list-file' '/usr/local/psa/var/modules/panel-migrator/sessions/20170722154640/migration-list.json' '--task-id' '2017-07-22-15-47-48' EXIT CODE: 1 STDOUT: [2017-07-22 15:47:49][INFO] Initialize Plesk Migrator [2017-07-22 15:47:49][INFO] Target Plesk host: 216.70.112.58 [2017-07-22 15:47:49][INFO] Source Plesk 'source' host: 64.207.153.49 [2017-07-22 15:47:49][INFO] Target Plesk host: 216.70.112.58 [2017-07-22 15:47:49][ERROR] Failed to add new migration task Cause: 'list' object has no attribute 'iteritems' That is a critical error, migration was stopped. STDERR:

Any help would be greatly appreciated, as I'm under the gun to complete this migration in the next couple of days, and I'd rather not have to manually migrate everything.
 
Thanks UFHH01. I actually managed to solve the problem myself. I used advanced mode, and watched the progress of the migration logs on the server, and realized that the destination server had its IP set to Dedicated instead of Shared, which was the root cause.
 
Back
Top