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

404 Status Code

PDF
Focus Mode
Font Size
Last updated: 2024-12-30 22:04:50

Error Description

What should I do if a 404 status code is returned by a CDN domain name?

Cause

1. The origin server is exceptional.
2. The configuration of the origin server information and host header in the console are changed.

Solution

1. Check whether your origin server works properly.
2. Check whether configuration of the origin server information and host header in the console are correct.

Troubleshooting Procedure

1. Check whether your origin server is exceptional.
If it is so, fix the origin server.
If it is not, go to Step 2.
2. Check the configuration of the origin server information and host header in the console. Log in to the CDN console, select Domain Management, find the corresponding domain name, select Basic Configuration > Origin Server Information, and check whether the settings of Origin address and Host header are correct.
Origin type:
Customer origin server
If you select customer origin server, you should provide an IP address or domain name of the business server that can be normally accessed.
COS origin server
If you select a bucket in COS as the origin server, select Default Domain or Static Website based on your bucket configuration. If your bucket is private, authorize CDN and enable origin-pull authentication to turn on private bucket access.
Third-Party object storage
If you select a third-party object storage service, enter the valid bucket access address as the origin server. Currently, AWS S3 and Alibaba Cloud OSS are supported. If the bucket is private, enter a valid key and enable origin-pull authentication to turn on private bucket access.
Host header: It refers to the domain name accessed on the origin server by a CDN node during origin-pull. It defaults to the acceleration domain name. If a wildcard domain name is connected, it will be the actual access subdomain name by default and can be customized. (Note: it cannot be modified if the origin server type is COS or a third-party object storage service).
For more information on origin server configuration, see Origin Server Configuration.

Help and Support

Was this page helpful?

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

Feedback