- Plesk for Windows
- Migration fails with the following error:
Panel Migrator failed to connect to RPC Agent running on '203.0.113.2' server.Or:
RPC Agent is required for communication between current server and '203.0.113.2' server
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 First, check that Windows Administrator's credentials specified for the server are correct. If they are correct, it is very likely that File and Printer Sharing service is disabled on the remote server, so automatic start of agent is not possible. Try to upload RPC Agent installation package to the 203.0.113.2 server and run it manually.
RPC Agentis installed and running on the source server.
Network issue, required ports for migration are closed by a firewall.
Follow the steps that migration tool suggests in the output:
CONFIG_TEXT: 1. Check that there are no firewall rules blocking connections to 10155 port on 203.0.113.2 from that server.
Make sure you could connect to the source server by 10155 port with "telnet" utility running on that server.
2. Check that agent is running on the source server (panel-migrator-rpc-agent.exe process)
and listening on 10155 port. If it does not, try to start 'panel-migrator-rpc-agent.exe',
which is usually installed to "%SYSTEMDRIVE%\\panel-migrator\\rpc-agent\\". If it is still not running -
investigate debug.log and info.log files on 203.0.113.2 server
(which are usually located at"%SYSTEMDRIVE%\\panel-migrator\\rpc-agent\\ directory).
3. Try to upload RPC Agent installation package to the 203.0.113.2 server and run it manually.
The instructions on how to run RPC Agent manually can be found in this article.
Portqryutilities to ensure that all the ports listed below are accessible:
CONFIG_TEXT: 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.
Make sure that firewall is properly configured, as it may affect communication between the source and target servers, or temporarily disable it if it does not restrict your security requirements. Enable it back once a migration is finished.