- Plesk 12.5 for Linux
- Plesk Onyx for Linux
- Plesk 11.x for Linux
- Plesk 12.5 for Windows
Plesk Migrator fails with following error from GUI:
Error: Unable to start migration. Please check specified IP address, administrator login and password and try again. If issue still reproduced, refer logs to further investigation.
On target host
has the following data:
+|2015-11-02_08:25:24,017|D|MT|core.workflow.runner.by_subscription|||Checking whether it is required to execute action
+|2015-11-02_08:25:24,017|D|MT|core.workflow.runner.by_subscription|||START: Get operation progress in current session
+|2015-11-02_08:25:24,017|D|MT|core.workflow.runner.by_subscription|||FINISH: Get operation progress in current session
+|2015-11-02_08:25:24,017|D|MT|core.workflow.runner.by_subscription|||Exit common action block
files on the destination server have the following error:
URLError: <urlopen error [Errno 10054] An existing connection was forcibly closed by the remote host> PleskConnectionCheckError: Failed to connect to target Plesk server by Plesk API: <urlopen error [Errno 10054] An existing connection was forcibly closed by the remote host>
Target server behind NAT or some ports are blocked by firewall.
Ensure that firewall is configured to pass the following ports:
TCP ports 135, 139, 445 and UDP ports 137, 138. Be sure to open these ports on the source and on the target server.
TCP port 1433 for MS SQL, if it is used as the default instance.
UDP port 1434 and all (or manually selected) TCP ports for MS SQL, if it is used as a named instance.
TCP port 10155 for a custom Plesk Migrator service performing miscellaneous tasks.
TCP port 10156 for rsync server.
TCP port 8443 for access to Plesk XML API on the target server and on the source servers, if migrating from Plesk.
TCP ports 110, 143 for POP3 and IMAP, on source and target servers. These are used for post-migration checks.
Ensure that UAC (User Account Control) is disabled in case if username provided as 'administrator login' member of Administrators group, but not Windows administrator.
Ensure that target server is not behind NAT and routing is configured properly.
Additional information is available in Migration Guide