What are the username and password for remote logins?
Username and password for logging in to a cloud server:
Username for Windows: Administrator
Username for Linux: root
If you forgot the login password or did not set a password when creating the cloud server, you can reset the password.
What should I do if my ECS instance is logged in from a different location?
If your ECS is logged in from a different location, the solution is as follows:
1. Check whether you or another administrator logged in to the ECS at the time of login from a different location.
2. If the ECS was not logged in by a legal administrator, you can do the following:
Reset your password immediately.
Check whether you are attacked by viruses.
Use the security group feature to only allow the login from specific IP addresses.
What should I do if I cannot remotely log in to a Windows cloud server?
If you cannot remotely log in to a Windows cloud server, perform the following steps to troubleshoot:
1. Check whether the EIP can be pinged.
If the EIP cannot be pinged, see "What should I do if the EIP of the cloud server cannot be pinged?" in the directory on the far right of this page to run the troubleshooting procedure.
If the EIP can be pinged, go to Step 2.
2. Check whether port 3389 of the ECS can be accessed.
If port 3389 cannot be accessed, check whether port 3389 is allowed in the security group.
If it can be accessed, go to Step 3.
3. Check whether the RDP service on the ECS is abnormal.
Log in to another Windows cloud server in the same Intranet CIDR block and remotely log in to the faulty cloud server on this server.
If the remote login fails, the RDP service may be abnormal. Log in to the faulty cloud server using VNC to check whether the RDP service is abnormal. Then, restart the RDP service, and try to connect again.
Restart the RDP service as follows:
Click Start, select Run, and enter services.msc.
In the list of services, select Remote Desktop Services and restart the service.
4. Check whether the remote connection port of the ECS has been modified.
In HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber, check whether the configured port is port 3389 by default. If not, change the port to the configured port during remote connection.
5. Check whether the number of connections is limited for the ECS.
Check the remote desktop configuration inside the OS:
Click Start, select Run, and enter gpedit.msc to open Group Policy Editor.
Select Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections, enable Limit number of connections, and check if the limit is enabled.
Note：If there is a maximum number of connections configured, it may cause the connection to the Windows ECS to fail through remote login. If multiple users are logging in to the cloud server at the same time and the number of connections exceeds the maximum number of connections, users beyond the maximum number of connections cannot receive the arbitration from the cloud server, resulting in the session staying in the configuring state. Please select to disable the configuration or set a larger maximum number of connections.
6. Other Solutions
If you still cannot connect to the Windows instance after you have completed all the above troubleshooting steps, save the self-diagnosis result and submit a ticket on the eSurfing Cloud console to call technical support for help.
What should I do if I cannot remotely log in to a Linux cloud server?
If you cannot remotely log in to a Linux cloud server, perform the following steps to troubleshoot:
1. Check whether the resource status is normal.
On the console, check whether the cloud server resources are in the Running state. If the cloud server is in the Stopped State, restart the cloud server before logging in to it.
2. Check the login credential.
Check the login credential that you set when creating the ECS.
Password: Check whether the login password used is accurate. If you forgot the password, you can reset the login password of the cloud server. After the password is reset, make sure that the cloud server has been restarted for the new password to take effect.
Setting after creating a cloud server: If you have not set a login credential when creating a cloud server, click Reset Password in the Operation column after the ECS is created, and set a password for the ECS as prompted. Make sure that the cloud server has been restarted for the new password to take effect.
3. Check whether the cloud server load is too high.
High bandwidth and CPU usage of the cloud server may result in login failure. You can create an alarm task using Cloud Eye. The system automatically sends you an alarm notification when the bandwidth or CPU usage reaches the threshold specified in the rule.
If you cannot log in to the ECS due to high CPU usage, perform the following steps to reduce CPU usage:
Turn off some processes that are not in use for a while.
Restart the cloud server.
Change the specifications of the cloud server to upgrade the vCPU and memory.
Check whether the login failure is caused by the bandwidth exceeding the limit. If so, consider increasing the bandwidth. For details about how to increase the bandwidth, see EIP > Modify the Bandwidth.
After all the above steps are complete, remotely connect to the cloud server again.
4. Check whether the security group is correctly configured.
On the details page of the cloud server, select the Security Group tab to check that port 22 has been added to the inbound rules of the security group.
If not, add port 22 in the inbound direction. For details, see VPC > Add a Security Group Rule.
After all the above steps are complete, remotely connect to the cloud server again.
5. Other Solutions
If you still cannot connect to the Linux instance after you have completed all the above troubleshooting steps, save the self-diagnosis result and submit a ticket on the eSurfing Cloud console to call technical support for help.
After I have remotely logged in to the ECS using VNC, why cannot I copy and send 3,000 local characters to the cloud server at one time as described?
This may be caused by the following two reasons:
1. The server was purchased earlier, so you need to manually upgrade the feature. For the specific upgrade method, you need to shut down the cloud server and restart it before completing the update. Before shutting down the server, please save your data to prevent data loss.
2. The following server specifications do not support 3,000 characters, but can support up to 160 characters. The actual situation is subject to the displayed information on the console:
Cloud server: s2
GPU cloud servers: P2v, G5, PI2, G6, P2vs, and G5s.
What should I do if the EIP of the cloud server cannot be pinged?
Perform the following steps to troubleshoot the EIP ping failure:
1. Check the security group rules. Check whether the security group corresponding to the ECS NIC allows the ICMP rule in the Inbound direction. You can meet any of the following rules.
2. Check the Network ACL rule. Check the Network ACL status. The following figure shows a network ACL example in enabled and disabled states.
Check whether the NIC associated with the EIP is in the subnet associated with the Network ACL, as shown in the figures below:
Associated subnet:
Inbound:
Outbound:
If Network ACL is enabled, you need to add an ICMP permission rule to allow traffic.
Note：Note that the default rule of Network ACL is to drop all packets of inbound and outbound directions. If Network ACL is disabled, the default rule still works.
3. Check whether the default route exists on the ECS.
Log in to the ECS and run the following command to check whether there is a default route:
# ip route
If there is no default route, run the following command to add one:
# ip route add default via XXXX dev eth0
Note：XXXX indicates the gateway IP address.
4. Run ping tests on other ECSs in the same region.
Ping the EIPs of other ECS in the same region. If they can be pinged, the virtual network runs normally. Call the basic network technical support for help.
5. Use the Webmaster Tools to run ping tests.
Sign in to the Webmaster Tools website http://ping.chinaz.com/.
Enter an EIP and click Ping Test. The following uses 122.112.197.21 as an example.
If most of the monitoring points can be pinged, please check your local network.
6. View the traffic monitoring details of the EIP in Cloud Eye.
Log in to the Cloud Eye console to view the traffic of the EIP and check whether the bandwidth of the EIP is fully occupied.
7. Troubleshoot the internal configuration of the ECS.
Check whether the ECS is configured with multiple NICs. If it is configured with multiple NICs and the EIP is bound to a non-primary NIC, you need to configure policy-based routes inside the ECS.
Log in to the ECS to check whether the NIC is created and whether the NIC has been assigned a private IP address. If you cannot log in to the ECS using the password you set, submit a ticket to call eSurfing Cloud technical support for help.
If the NIC is not created correctly, or the NIC has been created but the private IP address has not been assigned to it, submit a ticket to call eSurfing Cloud technical support for help.
Run the top command to check whether the CPU usage of the ECS is high.
If the ECS runs the Linux OS, run the iptables-save command to check whether the ECS is restricted by security rules.
If the ECS runs the Windows OS, check whether the firewall of the ECS is restricted.
Troubleshoot the disconnection from ports.
If the ECS passes the ping test, but the access to a specific port is still not available and the port number is within the range shown in the figure below, you need to change the service port as the following ports are blocked by the carrier.
If you cannot access a specific port of the ECS, you need to check whether the security group rules and the network ACL allow this service port.
Log in to the ECS and run the following command to check whether this port is listened on the ECS:
# netstat – na | grep XXX
Note：XXXX indicates the gateway IP address.
How do I prepare for logging in to an ECS?
For Windows OSs
1. Obtain the login password.
Use the password you set when creating the cloud server to log in to the ECS. If you forgot the password, you can reset the password.
2. When logging in the ECS using MSTSC, you need to ensure that the an EIP is bound to the cloud server and the remote desktop protocol is enabled. If not, you can bind an EIP and use the remote login tool on the console to log in to the cloud server to enable the remote desktop protocol.
For Linux OS
1. Obtain the login password or key pair.
Use the password you set when creating the cloud server or the bound key pair. If you forgot the password, you can reset the password.
2. When logging in to the ECS using SSH, you need to ensure that an EIP is bound to the cloud server.
What should I do if I forget my password?
If you forgot the login password, you can reset a new password.
You can reset your password in the ECS console and then log in again with the new password. To reset the password, perform the following steps:
1. Log in to the console and click ECS to go to the ECS list page.
2. Select the ECS for which you need to reset the password, and click More.
3. In the drop-down menu that pops up, select Reset Password.
4. In the pop-up window, enter a new password and confirm that it is correct. Please note that the password contains 8 to 30 characters in length, which must contain three of these types (uppercase letters, lowercase letters, numbers, and special characters "()`~!@#$%^&*_-+=|{}[]:;'<>,.?/"), cannot start with a forward slash (/), and cannot contain consecutive characters.
5. Click OK. A system prompt appears, indicating that your password has been reset successfully.
6. Use the new password to log in to the ECS console and perform follow-up operations.
For more information, see Reset the Password on the console.
What should I do if the page does not respond after I log in to an ECS using VNC and do not perform any operation for a long period of time?
If you log in to the ECS using VNC, but do not perform any operation for a long period of time, the VNC login interface may not respond, and your keyboard and mouse also do not work normally. In this case, try to restart the cloud server to solve the problem.
To restart the cloud server, perform the following steps:
1. Open Terminal or the CLI window.
2. Click Send CtrlAltDel on the top right.
3. Wait for a while to make sure the cloud server has been restarted.
Note that restarting the cloud server will interrupt ongoing tasks, so make sure you save all unsaved work before the cloud server restart. If you still have any problems after restarting the cloud server, submit a ticket or contact customer service at 400-810-9889 for technical support.
What should I do if no audio file can be properly played on my ECS logged in using VNC?
When you log in to your Windows ECS using VNC, audio files fail to be played, because VNC does not support audio playing.
You can log in to the ECS using MSTSC to play the audio files.
1. On the local computer, enter mstsc and click OK. The Remote Desktop Connection window is displayed.
2. Click Options in the lower left corner and click the Local Resources tab.
3. In the Remote audio pane, click Settings to configure remote audio settings.
4. In the Remote audio playback pane, select Play on this computer.
How can I change the resolution of a Windows ECS?
The procedure for modifying the resolution of a Windows ECS varies with the version of Windows OS. This section takes the Windows Server 2012 Data Center edition as an example.
Login Using VNC
Log in to the ECS using VNC. Right-click the desktop and select Screen Resolution. On the pop-up page, select the appropriate resolution, and click OK and Apply.
Login Using MSTSC
1. On the local computer, enter mstsc and click OK. The Remote Desktop Connection window is displayed.
2. Click the Display tab. Then, in the Display configuration pane, set the resolution.
3. After the resolution setting is complete, use MSTSC to log in to the ECS.
How do I change the port for remote login?
This section takes the Windows Server 2012 Data Center edition as an example to describe how to change the default port of a Windows ECS instance for remote login.
1. Log in to the console.
2. Select 
East China - East China 1.
3. Select 计算 > 弹性云主机 to enter the cloud server console.
4. See Remotely Log in to the Windows ECS Console (Using VNC) to remotely log in to the Windows ECS instance with the port for remote login to be changed.
5. Modify the value of the registry subkey PortNumber.
1) Right-click on the Windows key and select Run to launch the Run window.
2) In the text box of the Run window, enter regedit.exe, and then press Enter to open the registry editor.
3) In the left navigation tree, select HKEY_LOCAL_MACHINE >Select System > CurrentControlSet > Control > Terminal Server > Wds > rdpwd > TDS > tcp, as shown in the figure below:
4) Find the registry subkey PortNumber in the list and right-click it to enter the modification window.
5) In the pop-up dialog box, enter the new port number for remote login in the text box of the numeric data, for example, 3398. In the radix box, select Decimal, and then click OK.
6) In the left navigation tree, select HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control > Terminal Server > WinStations > RDP-Tcp.
7) Find the registry subkey PortNumber in Right the list and right-click it to enter the modification window (Use the keyboard arrow key to look down).
8) In the pop-up dialog box, enter the new remote port number for remote login in the text box of the numeric data, which in this case is 3398. In the radix box, select Decimal, and then click OK.
6. Restart the cloud server on the ECS console, as shown in the figure below:
7. Add a security group rule to the instance to allow the newly configured port 3398 for remote login to be connected to.
For details, see Configure a Security Group Rule.
8. At last, use the remote desktop connection feature to remotely log in to the instance. Now you can remotely connect to the instance by adding the new port number 3398 to end of the remote IP address.
This section takes CentOS 8.0 64-bit as an example to describe how to change the default port of a Linux ECS instance for remote login.
1. Log in to the console.
2. Select East China - East China 1.
3. Select 计算 > 弹性云主机 to enter the cloud server console.
4. In the row of the ECS for which you want to change the port for remote login, click Operation > Remote Login to remotely connect to the ECS instance.
5. Enter the username root and the password you set when purchasing the ECS to successfully log in to the ECS, as shown in the figure below:
6. Since sshd_config is an important configuration file in Linux OSs, in order to avoid failures caused by misoperation, please run the following command to back up the sshd_config configuration file before running a Linux ECS:
# cp /etc/ssh/sshd_config /etc/ssh/sshd_config_bak
7. Go to the /etc/ssh directory and enter the ll command to view the following information:
# ll # cp /etc/ssh/sshd_config /etc/ssh/sshd_config_bak
8. Change the port number of the sshd service. Considering it is already in the /etc/ssh path, run vim sshd_config directly to edit the sshd_config configuration file. Press i on the keyboard to enter the edit mode, and add the new remote service port. This section takes port 2222 as an example. Under Port 22, enter port 2222.
9. Press Esc on your keyboard and enter :wq to save and exit the edit mode.
10. Run the following command to restart the sshd service:
# systemctl restart sshd
At this point, the default port for remote login of this ECS has been changed from 22 to 2222.
Functional Verification:
1. Open the remote connection tool putty, enter the EIP of this ECS instance, and log in to this ECS instance with the default port 22 first. You can see that the connection is rejected and the network connection has been interrupted, which means that port 22 is no longer able to be used for remote login.
2. Configure a security group for the instance and allow the TCP port 2222. For detailed operations, see Configure a Security Group Rule
3. After the configuration is complete, use SSH to connect to the new port 2222, and enter 2222 in the Port field to check that the connection can be successfully completed.
Why cannot I log in to a Linux ECS with the new port after the default SSH port of the Linux ECS has been changed?
You may not be able to log in to a Linux ECS with a new port due to the following reasons: The security group does not allow access to the new port; the firewall does not allow access to the new port; or the new port is not added to the sshd file.
Check the security group rule.
For example, if the new SSH port number is 2222, there needs to be a security group rule that allows port 2222 in the inbound direction. If no such rule exists, you must add port 2222 in the inbound direction of the security group.
Check the firewall rule.
Check whether the iptables firewall allows access to the new SSH port. In this case, take port 2222 as an example.
1) Log in to the Linux ECS. For example, run the following command to edit the iptables file on a Linux ECS running CentOS 7.6:
# vi /etc/sysconfig/iptables
2) Add the port 2222 rule.
-A INPUT -m state -state NEW -m tcp -p tcp -dport 2222 -j ACCEPT
3) Restart the iptables service after the modification is complete.
# systemctl restart iptables
Check the SSH configuration file.
1) Log in to the ECS to check the SSH configuration file. Run the following command to check whether port 2222 is configured:
# vi /etc/ssh/sshd_config
2) If it is not configured, replace #Port 22 with Port 2222.
3) Run the following command to restart the SSH service:
# service sshd restart