Resolving Issues with the Registration of Source Plesk Servers

Common Issues

Issue: The migration manager could not connect to 'domain.name' via the SSH protocol. Ensure that the server is up and that there are no firewall rules that may block SSH connection to the server.

Resolution:

Check whether the server is running and responds. The following is a command to execute and an expected response.

[root@server1 ~]# ping -c 2 example.com
PING example.com (93.184.216.34) 56(84) bytes of data.
64 bytes from www.example.com (93.184.216.34): icmp_seq=1 ttl=41 time=241 ms
64 bytes from www.example.com (93.184.216.34): icmp_seq=2 ttl=41 time=241 ms
--- example.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 241.181/241.181/241.182/0.491 ms

If the server is not reachable, start it and perform this check again.

Make sure that SSH is listening on the standard port 22. Connection over the SSH protocol is supported only on the default port 22 (TCP and UDP). If you have closed the port 22 and configured SSH to listen on a non-standard port, for example, 10022, you can temporarily reconfigure SSH to listen on the port 22 during migration, or configure data forwarding from the default port 22 to the non-standard port 10022.

To check if the connection over SSH can be established over the port 22, issue the following command:
```
# telnet example.com 22
Trying example.com...
Connected to example.com.
Escape character is '^]'.
SSH-2.0-OpenSSH_5.3.
```
Check if it is possible to connect over SSH with the username and password that you chose (from the management node to OBAS and all its service nodes; from Plesk servers under OBAS to Plesk servers under the WebHosting Plesk Module and vice versa; from the management node to OBAS Plesk servers over IMAP):
```
ssh username@example.com
```
If connection cannot be established, but the firewall is enabled on the server, configure the firewall to allow incoming SSH connections from other servers. Additionally, review the files /etc/hosts.allow and /etc/hosts.deny for any rules that may prevent access to the SSH service from the destination servers.

For example, if access to the sshd service is denied in /etc/hosts.deny:
```
`sshd: ALL `
```
or
```
`ALL: ALL `
```
then, /etc/hosts.allow should have a record that would allow SSH access from the destination server:
```
`sshd: 192.0.2.2 192.0.2.3 : allow `
```
Replace the IP addresses above with the IP address of the destination server. If the destination server has several IP addresses, put all of them in one line, separating with whitespace characters.
Check if the user account under which the connection is established is allowed to run commands with superuser privileges. The command to execute on the source server and an expected response are shown below.
```
[user1@server1 ~]# sudo -v && echo $?
0
```
If the response is not received, ask the system administrator to grant superuser privileges to the user with the specified username, or run the following command under the “root” user:
```
[root@server1 ~]# visudo
```
A file that defines sudo privileges will open in a text editor. Now you need to add the user to this file to grant the desired access rights.

Find the part of the file that is labeled "User privilege specification". It should look as follows:
```
# User privilege specification
root ALL=(ALL:ALL) ALL
```
To provide the user with sudo privileges, copy the line beginning with "root" and paste it in the row below, replacing the user "root" on the new line with the appropriate username:
```
# User privilege specification
root ALL=(ALL:ALL) ALL
user1 ALL=(ALL:ALL) ALL
```
Save the file and close it. By default, you can do that by pressing Ctrl-X, and then typing "Y", and pressing "Enter".

Issue: The migration manager could not connect to 'domain.name' via the SMB protocol. Ensure that the server is up and that the SMB service is operating on the Windows server.

Resolution:

Check whether the SMB service is running on the server. The commands that you need to execute in the console on the host where the Migration Manager is installed and an expected result are shown below.

[root@server1 ~]# smbclient -U Administrator -L example.com
Enter Administrator's password:
Domain=[PPW12-5] OS=[Windows Server 2012 R2 Standard 9600] Server=[Windows Server 2012 R2 Standard 6.3]
Sharename Type Comment
--------- ---- -------
ADMIN$ Disk Remote Admin
C$ Disk Default share
IPC$ IPC Remote IPC

If the SMB server is not running, start it from the server’s command line:
```
> net start workstation
```
If the command fails with the error “System error 1058 has occurred”, you first need to enable the service by executing the following command:
```
> sc config lanmanworkstation start= demand
```
After the service is enabled, try starting it again.

Issue: The following services are not running: <a list of services>. Please start them.

Resolution:

To start the services, execute the following command on the source server for each service listed in <list>:

For Linux-based systems:

# /etc/init.d/{SERVICE_NAME} start

# systemctl start {SERVICE_NAME}

For Windows-based systems:
```
> net start {SERVICE_NAME}
```

Plesk Issues

Issue: The system could not connect to the Plesk XML API {PLESK_API_URL} on the server {HOSTNAME}. Check whether the firewall allows connections to the port 8443.

Resolution: Make sure that the TCP port 8443 is accessible on the source system. You can do so by executing the following command in the server console, on the host where the migration tool is installed:

[root@server1 ~]# </dev/tcp/{HOSTNAME}/8443 && echo OK || echo FAILED
OK

[root@server1 ~]# nc -vw5 {HOSTNAME} 8443
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connected to {HOSTNAME}:8443.

If the port is not accessible, run the following command on the source system:

[root@server1 ~]# iptables -A INPUT -p tcp --dport 8443 -j ACCEPT

Issue: The system could not connect to the Plesk XML API {PLESK_API_URL} on the server {HOSTNAME}.

Resolution:

Check whether all services critical for migration are running. (They are listed in the Readiness for migration section.)

The services that are critical for migration are listed below.

Plesk for Linux:
Version earlier than 11.5:
- Control panel’s web server: sw-cp-server or psa
- MySQL: mysql or mysqld or mariadb
Version 11.5 or later:
- Control panel’s web server: sw-cp-server
- Control panel engine: sw-engine
- MySQL: mysql or mysqld or mariadb
Learn more about how to check the status of these services at https://kb.plesk.com/en/111283.
Plesk for Windows:
- Control panel: plesksrv
- Control panel’s database: PleskSqlServer
- IIS web server: W3SVC
Learn more about how to check the status of these services at https://kb.plesk.com/en/111289.

If any of these services are not running, start them as described in the knowledge base articles.

Issue: The license key for Plesk on the source node is invalid.

Resolution: Migration is possible only if a valid Plesk license is installed on the source Plesk server. To resolve issues with a Plesk license, log in to Plesk as admin and check the license key's expiration date:

If the key expiration date is in the future, check the system's date and time by running the date command in the Linux shell or date /T in the Windows console. If they are incorrect, correct them.

If the key expiration date is in the past, it means that the key is expired. Refer to this article for further troubleshooting: https://kb.plesk.com/115731.

Issue: Microsoft .NET Framework version 4 is not installed.

Resolution:

Plesk Migration Agent for Windows requires Microsoft .NET Framework 4 installed on the source server. To install Microsoft .NET Framework 4, follow the instructions at https://www.microsoft.com/en-us/download/details.aspx?id=17851.