SymptomsThe following warning is shown when starting a new migration via Plesk Migration Manager:
Network connection failed. Cannot connect to Plesk Migration Agent on the remote host
CauseCertain machines or network configurations may cause connectivity problems between Plesk Migration Manager and Migration Agent. For example, the error may be shown if Parallels Plesk Panel includes an address from a local subnet (like the address from the 192.168.0.0/24 subnet).
If you experience this problem, do the following*:
- Stop the migration.
- Stop Migration Agent (close its window).
Check the IP address key value in the Migration Agent configuration file,
If the key is not specified, or is set to
0.0.0.0, specify a valid IP address for the key.
If a specific IP address is set for the
IP addresskey in the
WINAgentMng.exe.configfile, make sure that it is a valid address and that it is the same as the address entered in the Source host field on the Remote Host Connection Setup screen during the migration setup. If it is different, either set the value of the key to "
0.0.0.0" or remove the key from the
- If the key is not specified, or is set to
- Start Migration Agent.
Initialize a new migration session. On the Remote Host Connection Setup screen, type the IP address specified in the
IP addresskey in the
WINAgentMng.exe.configfile into the Source host field under Remote host connection settings.
- Proceed with the migration as described in the "Performing Migration" section.
* - If Plesk Migration Manager is installed behind an NAT and you experience this problem, it cannot be resolved in such a way. You should get both servers to connect without the NAT between them and enable the migration.
If connection without NAT is not possible, the problem can be workarounded by ports transmission. The following ports should be transmitted:
- Plesk Migration Agent - port 6489
Backup copying from the source server.
- Port 443 - Default
SMB ports in case of SMB is used instead of SSL for data transfer described in the article #112215.
- TCP 135
- TCP 139
- TCP 445
- UDP 137
- UDP 138
If Parallels Plesk Panel includes an address from a local subnet and the solution above does not help, you should remove the local subnet addresses on the source server temporarily.