Troubleshooting Guide for EdgeOne 4XX/5XX Status Codes

Recent Pages

Troubleshooting Guide for EdgeOne 4XX/5XX Status Codes

Last updated: 2024-12-16 12:02:13
After connection to EdgeOne, if your business request encounters a 4XX/5XX status code, you can troubleshoot by referring to the following common causes and solutions.
Note:
If you are still unable to resolve the issue by referring to the following troubleshooting guide, you can contact us. To facilitate troubleshooting, please provide EO-LOG-UUID information. If it is unavailable, please provide the following details:
User IP and EdgeOne node IP;
Specific 4XX/5XX error code and message;
Time and timezone for the 4XX/5XX error;
The URL causing the HTTP 4XX/5XX error (for example, https://www.example.com/images/icons/image1.png:).
HTTP 400
1. Meaning: The server cannot or will not process the request due to certain causes that are considered client errors (such as request syntax errors, invalid request message formats, or deceptive request routing).
2. Possible causes and solutions:
Origin server response: Test direct access to the origin server. If the origin server responds with 400, then modify the origin server configuration or adjust the client request behavior to obtain a correct response.
EdgeOne node response:
Check whether the request method is within the scope supported by EdgeOne. If it is not one of the following request methods, EdgeOne nodes will directly respond with a 400 status code.
GET, HEAD, POST, PUT, DELETE, TRACE, CONNECT, OPTIONS, PATCH, COPY, LOCK, MKCOL, MOVE, PROPFIND, PROPPATCH, and UNLOCK.
Protocol format errors, such as accessing HTTP via Port 443.
The HTTP request does not comply with RFC standards.
HTTP 403
1. Meaning: The server cannot or will not process the request due to certain causes that are considered client errors (such as request syntax errors, invalid request message formats, or deceptive request routing).
2. Possible causes and solutions:
Origin server response: Test direct access to the origin server. If the origin server responds with 403, then modify the origin server configuration or adjust the client request behavior to obtain a correct response.
EdgeOne node response: A common cause is failure to pass the hotlink protection verification.
Check whether HTTP response has been configured in the rule engine. If so, verify whether it hits basic access controls such as referer blocklist/allowlist, IP blocklist/allowlist, and user-agent blocklist/allowlist.
Check whether token authentication has been configured in the rule engine. If so, verify whether the URL in the client request has an expired timestamp or an incorrect MD5 encrypted string.
Check whether remote authentication has been configured through the edge function. If so, verify whether the URL in the client request does not comply with the authentication and release rules of the authentication server.
HTTP 416
1. Meaning: The server cannot process the requested data range. The most common situation is that the requested data range is not within the file range,
2. Possible causes and solutions:
Origin server response: Test direct access to the origin server. If the origin server responds with 416, then modify the origin server configuration or adjust the client request behavior to obtain a correct response.
EdgeOne node response:
Abnormal range values, such as: rangeStart < 0, rangeStart > rangeEnd, and rangeStart > FileSize.
The range header of the client request is not standard. For example, the request is Range: Bytes=0-1023 instead of Range: bytes=0-1023.
HTTP 418
1. Meaning: This response is typically used by servers to handle requests they do not want to deal with.
2. Possible causes and solutions:
Origin server response: Test direct access to the origin server. If the origin server responds with 418, then modify the origin server configuration or adjust the client request behavior to obtain a correct response.
EdgeOne node response: For a domain name connected to EdgeOne, the system automatically assigns service nodes to the domain name, and the corresponding nodes issue the configuration file for the domain name. The file content depends on the domain name's configuration, such as the origin server, cache, and header. When a request reaches an EdgeOne node, the node will read the configuration file for the domain name. If the configuration file is not found, a 418 status code will be returned.
Example: A client requests the domain name http://example.com/test.jpg that has been connected to EdgeOne, and the relevant request configuration for the domain name exists on nodes 1.1.1.1 and 1.1.1.2. When a domain name request reaches these two nodes, they will read the configuration file for the domain name example.com and respond successfully. However, if a request reaches node 2.2.2.2, a 418 status code will be returned. Check whether the domain name is bound to a service node without the domain name example.com and whether the CNAME configuration is correct. If there are no issues, please contact us.
HTTP 423
1. Meaning: It indicates "locked". In the scenario of connection to EdgeOne, it generally means request loopback is triggered.
2. Possible causes and solutions:
Origin server response: Test direct access to the origin server. If the origin server responds with 423, then modify the origin server configuration or adjust the client request behavior to obtain a correct response.
EdgeOne node response: Request loopback is triggered, that is, the CDN-Loop header's Loops value is ≥ 16. For details, see CDN-Loop. This is usually seen in accelerated domain names connected to EO, and accelerated domain names connected to EO or CDN are also set on the origin server.
HTTP 520
1. Meaning: EdgeOne's custom status code. After the node successfully establishes a TCP connection with the origin server, it initiates an HTTP request to the origin server. However, the origin server directly sends an RST packet, and the node responds to the client with a 520 status code.
﻿
2. Possible causes and solutions:
Origin server service exception: Test direct access to the origin server and capture packets to check whether the origin server responds to the HTTP request with an RST packet. This may be caused by the origin server's firewall or service exception.
HTTP 521
1. Meaning: EdgeOne's custom status code. When the node requests the origin server, if the origin server directly sends an RST packet during the TCP connection establishment phase, the node responds to the client with a 521 status code.
﻿
2. Possible causes and solutions:
Origin server service exception: Test direct access to the origin server. You can use a command tool such as curl or telnet to check whether the TCP connection can be established. This is usually caused by certain ports of the origin server not being open to the public network or origin server node network issues.
HTTP 522
1. Meaning: EdgeOne's custom status code. When the node requests the origin server, if the origin server does not respond during the TCP connection establishment phase, causing the node to time out, the node responds to the client with a 522 status code.
﻿
2. Possible causes and solutions:
Origin server service exception: Test direct access to the origin server. You can use a command tool such as curl or telnet to check whether the TCP connection can be established. This is usually caused by certain ports of the origin server not being open to the public network or origin server node network issues.
HTTP 523
1. Meaning: EdgeOne's custom status code. If the origin server configured for the domain name is a domain name, then when the node requests the origin server, it needs to resolve the domain name to obtain the IP of the origin server. If the resolution fails, the node cannot request the origin and responds to the client with a 523 status code.
2. Possible causes and solutions:
Try using dig to resolve the origin server domain name to confirm whether it can be resolved normally.
If the origin server domain name can be resolved normally, please contact us.
HTTP 524
1. Meaning: EdgeOne's custom status code. After the node successfully establishes a connection with the origin server and sends a request to the origin server, if the origin server does not respond, causing the node to time out, the node responds to the client with a 524 status code.
﻿
2. Possible causes and solutions:
Origin server service exception: Test direct access to the origin server to check for a response to the HTTP request. If the origin server responds normally, you can try adjusting the origin-pull timeout. If the issue persists, please contact us.
HTTP 525
1. Meaning: EdgeOne's custom status code. If the origin-pull protocol is HTTPS, the node needs to perform an SSL handshake with the origin server when it requests the origin server. If the handshake fails, the node responds to the client with a 525 status code.
﻿
2. Possible causes and solutions:
Check whether the domain name's origin-pull protocol is configured as HTTPS, but the origin server has no certificate deployed. If so, you can change the origin-pull protocol to HTTP in the domain name management section or deploy the corresponding domain name certificate on the origin server.
Packet loss occurs due to network issues during the SSL handshake between the node and the origin server.
Failure to pass the origin-pull certificate validity verification. Currently, EdgeOne verifies the certificate's validity period by default.
﻿