Migration using Plesk Migrator fails: Rsync failed to copy files from the source server

Symptoms

• When starting migration of a subscription using Plesk Migrator, the task fails with one of the following error messages:

  PLESK_ERROR: Panel Migrator failed to start RPC Agent on '203.0.113.2' server.
  RPC Agent is required for communication between current server and '203.0.113.2' server

  PLESK_ERROR: [Errno 10054] An existing connection was forcibly closed by the remote host

  PLESK_ERROR: Migration tools tried to perform operation in 3 attempts: Rsync failed to copy files from the source server 'source' (203.0.113.2) to target Plesk server: This could happen because of a network connection issue. Run migration for that subscription once more.

• Website data of a subscription is not migrated. The following message is logged in the [Info] log:

  PLESK_INFO: Failed to copy web files for subscription 'example.com'
  Migration tools tried to perform operation in 3 attempts: Rsync failed to copy files from the source server 'source' (203.0.113.2) to target Plesk server: (10, '', 'rsync: failed to connect to 203.0.113.2 (203.0.113.2): Connection timed out (116)\nrsync error: error in socket IO (code 10) at clientserver.c(128) [Receiver=3.1.1]\n')
  This could happen because of a network connection issue. Run migration for that subscription once more.

Cause

The target (destination) server fails to connect to the source server via a port (or ports) required by Plesk Migrator, because this port is being filtered by firewall (either local or external).

Resolution

Verify that the source and destination servers can communicate with each other via the following ports:

• 135, 139, 445 (TCP) and 137, 138 (UDP) ports - for automatic deployment of RPC agent (panel-migrator-rpc-agent.exe)

  Note: Ports 135, 139, 445, 137, 138 are not required, if the RPC agent is started manually on the source server.

• 10155 (TCP) - for Plesk Migrator service
• 10156 (TCP) - for rsync server (website data migration)
• 1434 (TCP) - for SQL Server data migration, if used. If an SQL Server instance uses a custom port, allow connections to this port from the destination server IP address as well.

To check whther connection is successful or not, use the tnc utility in Windows PowerShell:

1. On the target (destination) server, start Windows PowerShell.

2. Run the command:

   PS tnc 203.0.113.2 -port 10155

   where

   • 203.0.113.2 - IP address of the source server
   • 10155 - port to connect