Login Failure Due to Server Isolation

Last updated: 2020-02-11 11:51:35

    This document describes how to resolve login failures if the CVM is isolated from the public network.


    The CVM may have been isolated because it violates current laws and regulations. You can use the following methods to check whether the CVM is isolated.


    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, all network access will be isolated. Developers can use a jump server to log in to the server.
    For details, see [Cloud Security Violation Levels Classification and Penalties Description].


    1. Delete the violating content as instructed by the internal message or text message. Resolve security risks and reinstall the system if necessary.
    2. If the violation is not caused by your own action, your CVM may have encountered malicious intrusion. To resolve this, see Host Security.
    3. After resolving security risks and deleting violating content, you can submit a ticket to contact customer service to remove the isolation.