What Should I Do If a CloudTable Cluster Cannot Be Connected?
Possible Causes |
Solutions |
---|---|
Creation failed, Sub-health, or Frozen is displayed in the Status column. |
|
The connection command, username, password, IP address, or port number is incorrect. |
|
The OS type or the version of the client is correct. |
|
The client is incorrectly installed. |
|
The ECSs are not in the same AZ, VPC, subnet, and security group as the cluster. |
Check the AZ, VPC, subnet, and security group displayed on the ECS details page and the cluster details page. |
The inbound and outbound rules of the security group are incorrect. |
On the cluster details page, click the security group name. On the displayed Security Groups page, click Manage Rules to check the inbound and outbound rules. If there is no inbound rule, press Windows+R to display the Run dialog box, enter cmd to open the cmd window, and enter ipconfig. The IP address of the local host is displayed. Click Add Rule, enter the obtained IP address, and try to connect to the cluster again. For details, see Configuring Security Group Rules. |
Your network is not connected to the Internet. |
Press Windows+R to display the Run dialog box, enter cmd to open the cmd window, and enter ping URL. |
The firewall blocks the access. |
Modify the firewall policy or temporarily disable the firewall. |
The proxy for accessing the Internet is not enabled. |
Enable the proxy. |

If you cannot determine the cause and rectify the fault, submit a service ticket to report it. Log in to the CloudTable console, choose More > Service Tickets and click Create Service Ticket. Create a ticket and submit it.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot