Login Failure Due to Server Isolation
Last updated: 2019-11-06 15:06:08PDF
This document introduces the solution for the problem where the CVM is disconnected with the internet and cannot be logged in.
The CVM may have been isolated because it violated the requirements of current laws and regulations. You can use the following methods to check whether the CVM is isolated.
- When a CVM is isolated from the public network, you will be notified of isolation due to violation or regulations through an internal message in the console or a text message.
Cause of the Problem
When a regulation violation or risk event occurs for a CVM, the offending machine will be partially isolated (except for the private network login port 22, 36000, and 3389, other network access is isolated. Developers can use a jump server to log in to the server.
For details, see Cloud Security Violation Levels Classification and Penalties Description.
- Delete the violating content as instructed by internal message or the text message. Resolve security risks and reinstall the system if necessary.
- If it is not your own action that leads to the violation, then your CVM may have been subject to malicious intrusion. To resolve this, see Host Security.
- After resolving security risks and deleting violating content, you can submit a ticket to contact customer service to remove the isolation.