tencent cloud

Content Delivery Network

Updates and Announcements
Release Notes
Announcements
User Tutorial
Product Introduction
Product Overview
Strengths
Use Cases
Term
Use Limits
CDN Performance Descriptions (Spot-check)
Purchase Guide
CDN Purchase Guide
ECDN Purchase Guide
Getting Started
Configuring CDN from Scratch
Adding Domain Names
CNAME Configuration
Domain Name Ownership Verification
FAQs about Domain Name Connection
Configuration Guide
Domain Management
Domain Name Configurations
Statistical Analysis
Purge and Prefetch
Log Management
EdgeOne
Service Query
Offline Cache
Permission Management
Permission Configuration
Console Permissions
Activate Real-time Logging as Sub-account/Collaborator
Use Cases
Accelerating Resources on COS with CDN
Practical Tutorial
Guide to Using the EdgeOne Tool for Migrating Content Delivery Network (CDN) Related Services
CDN - CVM
CDN - COS
Configuring CNAME via DNSPod
Regularly Storing CDN Logs
API Documentation
History
Introduction
API Category
Content Management APIs
Real-time Log APIs
Service Query APIs
Data Query APIs
Making API Requests
Log Query APIs
StopCdnDomain
Configuration Management APIs
Obsoleted APIs
Other APIs
Data Types
Error Codes
FAQ
Features
Billing
FAQs about Domain Name Connection
Cache Configuration FAQs
Purge and Prefetch
Statistical Analysis
FAQs about HTTPS
Connection
Errors
Troubleshooting Methods
Status Codes and Solutions
Node Cache Inconsistency
Slow Access Speed After CDN Activation
Low Traffic Hit Rate
404 Status Code
Page Display - CORS error
Resource Cache Failure
Service Level Agreement
Glossary

Status Codes and Solutions

PDF
Focus Mode
Font Size
Last updated: 2024-12-30 22:03:32
The table below explains the status codes of CDN.
Status Code
Meaning
Suggestion
400
HTTP request syntax error and the server cannot parse the request
Check whether the request syntax is correct.
403
Request is rejected
Check whether the request is blocked by access controls such as referer blocklist/allowlist, IP blocklist/allowlist, and authentication.
404
Server cannot return correct information
Check whether the original server is running normally, and whether the original server information or origin domain configurations are changed.
413
Content length of the POST request exceeds the limit
Check the content size of the POST request from the client (the maximum size is 32 MB by default).
414
URL length exceeds the limit
The maximum URL size is 2 KB by default.
423
Looping request
Check the 301/302 configuration, HTTPS origin-pull, and rewriting method of the origin server.
499
The client closes the connection
Check the client status and timeout configuration.
502
Gateway Error
Check whether the business origin server is normal.
503
COS frequency control is triggered
Check the cache configuration or whether the COS origin server returns no-cache/no-store.
509
Blocked due to CC attack
514
IP access frequency exceeds the limit
Check the IP access frequency control configuration in the CDN Console.
531
Error resolving the origin-pull domain name in the HTTP request
Check the domain name resolution configuration of the origin server.
532
Failed to establish a connection with the origin server in the HTTPS request
Check the port 443 status of the origin server, certificate configuration, or availability of the origin server.
533
Origin-pull connection timeout in the HTTPS request
Check the port 443 status of the origin server, certificate configuration, or availability of the origin server.
537
Origin server data reception timeout in the HTTPS request
Check the stability of the business origin server.
538
SSL handshake of HTTPS request failed
Check the compatibility between the origin server protocol and algorithm.
539
Certificate validation of HTTPS request failed
Check whether the certificate of the origin server is correctly configured (validity period and completeness of the certificate chain).
540
Certificate domain name validation of HTTPS request failed
Check whether the certificate of the origin server is correctly configured.
562
Failed to establish a connection in the HTTPS request
Please submit a ticket and provide the X-NWS-LOG-UUID information for troubleshooting.
563
Connection timeout in the HTTPS request
Please submit a ticket and provide the X-NWS-LOG-UUID information for troubleshooting.
564
HTTP origin request failed
If HTTP is configured as the origin request protocol, check the load and bandwidth utilization or access limit of the origin server. If the protocol is set to Follow Request, check the port 443 status and certificate configuration of the origin server. If no error is found in the origin server, please submit a ticket and provide the X-NWS-LOG-UUID information for troubleshooting.


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback