Before you begin
Before you start any load balancer troubleshooting procedure, ensure the following:
- Verify that the load balancer's VPC has security groups that allow the health check and the data path ports.
- Verify that the
health
field in each member isok
. If thehealth
field is shown asfaulted
orunknown
, ensure that the load balancer member's virtual server instance is responding to the load balancer health check requests by taking the following actions:- Verify in the load balancer member virtual server that a process (for example, an Nginx server) is running and listening on the back-end pool health monitor port.
- If the back-end pool health monitor port is not specified during the back-end pool creation, health check requests are sent to the member port. In this case, verify in the load balancer member virtual server that a process is running and listening on the load balancer member port.
Error codes
When making requests to the load balancer APIs, you might encounter errors. An error response contains an error code and a corresponding error message. For more information, see the VPC API reference.
Quota errors
Check the Quotas and service limits for the allowed quotas on load balancer resources.