Why Does CBH Login Fail Through an ECS in a New VPC Connected with the VPC Where CBH Is via VPN or a VPC Peering Connection
Symptom
- A VPC with a 10.xx.xx.xx CIDR block was selected for a CBH instance.
- This VPC was connected to another VPC with a 192. xx.xx.xx CIDR block via a VPN or VPC Peering connection.
- The CBH system can be accessed through the ECSs in the VPC with a 10.xx.xx.xx CIDR block.
- There is a low probability that the CBH system cannot be accessed through the ECS in the VPC with a 192.xx.xx.xx CIDR block.
- The route in the red box in the following figure was displayed in the network configurations of the CBH system.
Figure 1 Network configuration
Possible Causes
The CBH system uses a version earlier than 3.3.26.0. In versions earlier than 3.3.26.0, if a CBH system has a large number of requests, threads may be exceptionally stopped during system status checks. As a result, routes may fail to be refreshed, and request traffic is forwarded to ETH0 and then discarded. Login failures then occur.
Solutions
Upgrade the CBH system to 3.3.26.0. .
CBH System Login Failures FAQs
- How Do I Handle Login Exceptions?
- Why Is the IP Address or MAC Address Blocked When I Log In to the CBH System?
- Why Am I Seeing Error Code 404 When I Log In to the CBH System?
- Why Am I Seeing Error Code 499 When I Log In to the CBH System?
- What Are Possible Faults If I Log In to the CBH System as an Intranet User?
- Why Is a Host Inaccessible Through CBH?
- Why Does CBH Login Fail Through an ECS in a New VPC Connected with the VPC Where CBH Is via VPN or a VPC Peering Connection
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.
Chatbotmore