This document introduces the solution to the problem of being unable to log in to the CVM due to public network isolation.
Failure Symptoms
A CVM may be isolated because it violates current laws and regulations. You can check whether the server is isolated in the following ways.
- When the public network access of the CVM is isolated, you will be notified of the non-compliance and isolation through in-console message center or SMS.
- In the CVM console, the Monitoring/Status column displays the CVM status: In Isolation.
Causes of Problem
When a CVM has a non-compliance or risk event, the non-compliant server undergoes partial isolation (except for the ports 22, 36000, and 3389 of the private network, all other network accesses are isolated, and developers can log in to the server through a jump server).
Solution
- Follow the instructions in the message center or SMS to address the non-compliant content. Address the security risks and, if necessary, reinstall the operating system.
- If the violation was not caused by your personal actions, it is likely that your server has been maliciously compromised. For solutions, see Cloud Workload Protection.
- After you eliminate the security risks or stop the violation, contact customer service by submitting a ticket to lift the isolation.