What are the preparations before logging in to a physical server?
Windows Operating System
l Make sure that you have obtained the login password of the Windows-based physical server.
l Ensure that the physical server has already been bound to EIP for remote login.
Linux Operating System
l Make sure that you have obtained the login password of the Linux-based physical server.
l If you are using a remote login mode (for example, SSH), you do not need to bind the physical server to EIP. If you are using another login mode, for example, physical console or remote desktop, you must ensure that the physical server is bound to EIP for Internet access.
What should I do if I fail to log in to a Windows-based physical server?
If you fail to log in to a Windows-based physical server, shoot the trouble as follows:
Check whether login conditions are met
l Make sure you have the correct login credentials, including username and password.
l Make sure you have access to the physical server.
Check whether the network is normal
l Make sure your computer is on the same network as the physical server.
l Check whether the network connection is stable and eliminate the possibility of network failure.
Check whether the firewall is properly configured
l Make sure the firewall configuration of the physical server allows remote desktop connection.
l Check the firewall settings on the network where the physical server resides to ensure that the port is open.
Incorrect configuration of remote access port
l Check whether the remote desktop service is enabled for the physical server and listens to the correct port (default: 3389).
l Make sure that the port is not being used by another device on the network.
Try to restart the physical server
l If the problem persists, please create a ticket and contact the technical support for further troubleshooting help and solutions.
What can I do if I fail to log in to a Linux-based physical server?
When SSH login is unavailable to your physical server, we first recommend that you log in remotely from the console.
Can I log in remotely from the console?
When SSH login fails, please first try to remotely log in to the physical server from the management console.
1. Log in to the management console.
2. Go to Computing > Physical Server.
3. Select the physical server to log in to, and click Remote Login in the Operation column.
The connection is being established. You will be directed to the login screen about 1 minute later. Press Enter and enter username "root" and password.
Troubleshooting Steps
You can remotely log in to the physical server normally, but fail to log in to the physical server via SSH. We recommend that you shoot the trouble in the following steps:
1) Check whether the network is normal
l Make sure your computer is on the same network as the physical server.
l Check whether the network connection is stable and eliminate the possibility of network failure.
2) Check whether a security group is correctly configured
l Make sure that the configuration of the security group where the physical server resides allows SSH connection.
l Check that the security group rules are set correctly and that the SSH port (22 by default) is open.
3) Non-system disk information is not annotated in the /etc/fstab file
l Check whether the "/etc/fstab" file contains configurations for non-system disks (data disks) and ensure that these configurations are properly annotated or configured.
4) Incorrect configuration of remote access port
l Check whether the SSH service is enabled for the physical server and listens to the correct port (default: 22).
l Make sure that the port is not being used by another device on the network.
5) Too high CPU load
l Check the CPU usage of the physical server. If the CPU is overloaded, the SSH connection may fail.
l If the load is too high, try to free up the physical server resources or optimize the applications to reduce the CPU load.
If you still fail to remotely log in to the physical server by following the preceding instructions, record the resource information and the time of occurrence, create a ticket, and contact eSurfing Cloud technical support.
What is the browser version required to remotely log in to a physical server?
To log in to a physical server remotely, use a compatible browser version. The following lists the supported browser versions:
Browser | Version |
Google Chrome | 31.0-75.0 |
Mozilla FireFox | 27.0-62.0 |
Internet Explorer | 10.0-11.0 |
Please make sure that the browser version you are using falls within the above range for the best remote login experience. If your browser version is not on the supported list, we recommend that you upgrade to a compatible version or try another supported browser.
What should I do if the interface does not respond when I log in to a physical server remotely?
You can try the following solutions if the interface does not respond when you log in to a physical server remotely:
l Network connection stability: Ensure that your network connection is stable and has sufficient bandwidth. An unstable network connection can lead to slow response or disconnection of remote login.
l Reconnect: Try to close the remote login window and then reconnect to the physical server. Sometimes, reconnecting can temporarily solve the connection problem.
l Restart the physical server: If reconnecting does not work, restart the physical server. Restart the physical server in the console or using other appropriate means, and then try to log in remotely again.
l Check firewall and security group settings: Make sure your firewall and security group settings allow connections for remote login. Check that the corresponding port (such as an SSH port) is not blocked.
l Local client configuration: Try to update the version of the local client or remote desktop application. Make sure that the client you are using is compatible with the operating system the physical server is running on.
What should I do if the numeric key on the right of the input keyboard is displayed abnormally when I log in remotely?
You can try the following solutions if an exception occurs when you enter a number key on the right of the keyboard on the remote login page:
1. Use the setleds command: On the remote login interface, enter the following command to query the status of the numeric key.
setleds -F
If NumLock is off, the number key is off.
2. Run the following command to turn on the numeric key.
setleds +num
3. Run the following command again to confirm that NumLock has changed to On, and then you can use the numeric key on the right side of the keyboard to perform related operations.
setleds -F
Note:
The proceeding solutions apply to the Linux operating system. If you are using a different operating system or a different remote login tool, you may need to take another approach to resolve the issue.
What should I do if the SSH login or data transfer is slow?
Issue Description
In Linux instances, the SSH login or data transfer is slow over the Internet because the UseDNS feature is enabled for the SSH service.
The UseDNS feature is a security enhancement feature of the SSH service and is enabled by default. After this feature is enabled, the server performs DNS PTR reverse lookup based on the IP address of the client to obtain the name of the client. Then the forward DNS A record lookup is performed according to the obtained client name. Finally, the obtained IP address is consistent with the original IP address to prevent client spoofing. However, in general, the client uses a dynamic IP address and there is no corresponding PTR record. Therefore, when this feature is enabled, it cannot be used for information comparison. On the other hand, the operation delay is increased due to related lookup operations, which slows down the client connection.
Solutions
1. Log in to the physical server using the Remote Login function in the console.
2. Run the following command to open "/etc/ssh/sshd_config" in the vi editor.
vi /etc/ssh/sshd_config
3. Locate the following field:
#UseDNS yes
Add a line below this field and enter:
UseDNS no
4. Save your entry and restart SSH to take the changes into effect.
service sshd restart
By disabling the UseDNS feature, you should be able to increase the speed of SSH connection and data transfer. It should be noted that these operations require the root privilege or the corresponding administrator privilege.
If the problem persists, there may be other factors contributing to the slow speed, such as poor network connection and bandwidth limitation, and you can further investigate these factors.