Overview

This document lists some common fault scenarios during usage of Content Delivery Network (CDN). You can click the links to view troubleshooting procedures.

Symptom	Possible Causes
Why Is My Account Balance Deducted Even If I Have Purchased a Traffic Package?	You are not charged by traffic. You are using whole site acceleration. You are using CDN outside the region of your traffic package. The traffic used exceeds the traffic package quota.
Why Can't I Access a Web Page or Play a Video After I Enable CDN?	Your origin server is faulty. The domain name is not connected to CDN. The domain name configuration is incorrect. Your account is in arrears.
Why Is the Displayed or Downloaded Content Incorrect After CDN Acceleration Is Used?	Cache rules are incorrect. The incorrect content still exists in the local cache. CDN points of presence (PoPs) still store stale versions of your content. Files on multiple origin servers are inconsistent. The content is hijacked.
Why Is It Still Slow to Access a Domain Name That Has Been Added for CDN Acceleration?	The domain name is not connected to CDN. The CDN cache is not hit. Cross-carrier or cross-province access exists. Cache rules are inappropriate. The content is not prefetched. The client network connection is poor.
Why Is the Traffic Hit Ratio Low?	Origin server faults (for example, caching disabled on the origin server, high dynamic resource proportion, low website visits, and origin server failures) CDN faults (for example, inappropriate cache rules and frequent cache purge)
Why Does a Cache Prefetch Operation Fail?	Too many resources are prefetched. The cache time to live (TTL) is inappropriate. The origin server does not allow caching. The origin server cannot be accessed.
Why Is a 5XX Status Code Returned When I Request Resources from My Acceleration Domain Name?	Services on the origin server are faulty. The domain name configuration on CDN is incorrect. The origin server intercepts the request. The CDN PoP is abnormal.
Why Is a 4XX Status Code Returned When I Request Resources from My Acceleration Domain Name?	404: The origin server content is not found or the domain name configuration on CDN is incorrect. 403: The domain name is not connected to CDN, the origin server is faulty, or the request is intercepted due to the domain name configuration on CDN.
Why Does a 301/302 Redirect Loop Occur When I Request Resources from My Acceleration Domain Name?	The origin pull protocol and force redirect settings are incorrect.
Status Code and Handling Suggestions	-
Why Am I Getting a Permission Error Message?	The account permission is incorrect.
Why Can't I Log In to My Domain Name or Why Is the Information of Other Users Displayed?	Dynamic resources are cached.
Why Is the Cache of a Resource Inconsistent on Different PoPs?	All URL parameters are ignored. The cache is not purged after the content is updated on the origin server.
Why Does the Configured Cache Rule Not Take Effect?	Cache rule configuration was delivered but does not taken effect (wait about 5 minutes). The cache rule is incorrect.
What Do I Do If the Browser Displays a Message Indicating that a Cross-domain Exception Occurs After CDN Is Enabled?	The cross-origin resource sharing (CORS) settings are incorrect.
Why Is a File in an OBS Bucket with CDN Acceleration Enabled Be Automatically Downloaded When I Access the File?	The fault is caused by the default Object Storage Service (OBS) rule. Go to the CDN console, choose Domains in the navigation pane, click the domain name, click the Advanced Settings tab, and add the Content-Disposition response header with value inline.
Why Are All Files in the Bucket Displayed When Users Request a File from an OBS Bucket Connected to CDN?	If the origin server is an OBS public bucket, static website hosting is not enabled for the bucket. If the origin server is an OBS private bucket, the file list is displayed by default after access to the bucket is authorized.