SMS.3805 The Connection to the Port 22 of Target Server Timed Out

During a migration, an SSH connection must be established between the source server and the target server. This error message is displayed when OpenSSH reports the error "connect timeout", indicating that the SSH connection times out. As a result, the source server cannot connect to the IP address of the target server. The possible causes and solutions are:

• Check whether the security groups, firewalls, and ACL rules allow the source server to access the target server with the IP address.

  Check whether the connection is disallowed by any security groups, firewalls, or ACL rules on the network between the source and target servers. If it is, modify their settings to allow the source server to access the target server and retry the migration task.

• Check the network connectivity between the source and target servers. If a private network is used, check whether the source and target servers are in the same network range.

  Use SSH or Telnet to test the network connectivity between the source and target servers. If the connection fails, check the network and firewall settings.

  The commands are in the following format:

  • telnet <target-server-IP-address> <port>
  • ssh -p <port> <username>@<target-server-IP-address>

  By default, SMS connects to the target server using port 22. If the target server is configured to use a custom SSH port, replace <port> in the command with the actual port.

  For example, if the target server IP address is 192.168.0.x, you can run the following command on the source server as the root user to test connectivity to port 22:

  telnet 192.168.0.x 22

  ssh -p 22 root@192.168.0.x

• Check whether the target server is stopped.
  1. Sign in to the console.
  2. On the Elastic Cloud Server page, check the ECS (target server) status. If the ECS is stopped, choose More > Start in the Operation column.