How Can I Handle Error Codes?

Updated on 2024-04-19 GMT+08:00

View PDF

Common error codes include 400, 403, 502, and 504. If any of these codes is returned, it is recommended that you access the backend server to check if it can respond properly.

If the backend server responds properly, rectify the fault by referring to Table 1.

**Table 1** Common error codes
Error Code	Description	Possible Causes
400	Bad Request	The client sent a malformed request that does not comply with the HTTP specification. An HTTP request was sent to the HTTPS port. The size of the request header exceeded 64 KB.
401	Unauthorized	Authentication on the backend server failed. (This error code is returned to the client by the backend server.)
403	Forbidden	The request was intercepted by the backend server. (This error code is returned to the client by the backend server.)
404	Not Found	The backend server is abnormal or the application does not exist. (This error code is returned to the client by the backend server.) The forwarding policy was incorrectly configured, and the request was not routed to the right backend server.
408	Request Timeout	The client did not send the request within the time that the server was configured to wait, which is 60s by default. Sending a TCP keepalive packet does not prevent this timeout.
413	Payload Too Large	The size of the request body sent by the client exceeded 10 GB.
414	URI Too Long	The request URL or query string parameter sent by the client was too long.
499	Client Closed Request	The client disconnected from the load balancer before receiving a response from the load balancer. This error code is recorded only in access logs.
500	Internal Server Error	There was an internal error. (This error code is returned to the client by the backend server.)
501	Not Implemented	The load balancer failed to identify the request. The value of the Transfer-Encoding header field is not chunked or identity.
502	Bad Gateway	The port used by the backend server was incorrectly configured. The load balancer received a TCP RST packet from the backend server when attempting to establish a connection with or sending data to the backend server. The format of the response from the backend server was incorrect, or the response contained an invalid HTTP response header. The backend server is incorrectly configured, for example, incorrect routes or network ACL.
503	Service Unavailable	The application or backend server was unavailable. Generally, this error code is returned by the backend server.
504	Gateway Timeout	During the first connection, the load balancer fails to connect to the backend server before the connection times out. (The default timeout is 5 seconds). The load balancer established a connection with the backend server, but did not respond before the response timeout (which is 300s by default) elapsed. The network ACL of the subnet did not allow the load balancer to access backend servers in the subnet.

Parent topic: Service Abnormality

Previous topic: What Can I Do If ELB Can't Be Accessed or Traffic Routing is Interrupted?

Next topic: ELB Functionality

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot