Halaman ini belum tersedia dalam bahasa lokal Anda. Kami berusaha keras untuk menambahkan lebih banyak versi bahasa. Terima kasih atas dukungan Anda.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Show all

Help Center/ Content Delivery Network/ Troubleshooting/ Why Is a 5XX Status Code Returned When I Request Resources from My Acceleration Domain Name?

Why Is a 5XX Status Code Returned When I Request Resources from My Acceleration Domain Name?

Updated on 2024-06-06 GMT+08:00
  1. Visit the origin server to check whether a 5XX error occurs. For details, see How Do I Check Whether an Access Fault Is Caused by a CDN PoP or Origin Server?

    If the error occurs, check the origin server configuration. Data on the CDN console can help you troubleshoot certain origin server faults.

    • Log in to the CDN console. In the navigation pane, choose Analytics > Origin.

    • Check whether the bandwidth and traffic increase sharply. If the bandwidth and traffic increase sharply, the origin server will be overloaded and the response from the origin server will time out. Check whether resources are updated recently or new cache rules are configured for popular resources. When releasing new resources or functions, prefetch large files to CDN PoPs to prevent bandwidth bottlenecks caused by a large number of origin pull requests.
    • Check whether cache rules are configured on the origin server. If no-cache, private, or no-store is configured on the origin server and Origin Cache Control is enabled on the CDN console (this function is disabled by default), CDN cannot cache content and needs to pull content from the origin server. When a large number of origin pull requests are sent to the origin server, the response from the origin server may time out. For details about how to set cache rules, see Setting the Cache TTL.
    • Check whether the network of the origin server fluctuates. If the carrier network of the origin server is faulty, origin pull times out.

    If the origin server is normal, proceed to the next step.

  2. If the status code 504 is returned, locate the fault as follows.

    Cause: The origin server may not support the protocol used by CDN to pull content.

    1. The origin protocol used by CDN is same as the client access protocol.
      • If a client uses HTTPS to access CDN, CDN will use HTTPS to pull content from the origin server. If the origin server does not support HTTPS, it will return a 504 response.
      • If a client uses HTTP to access CDN, CDN will use HTTP to pull content from the origin server. If the origin server does not support HTTP, it will return a 504 response.
      • If a client uses HTTP to access CDN and you have configured force redirect to HTTPS on CDN, CDN will pull content from the origin server using HTTPS. If the origin server does not support HTTPS, it will return a 504 response.
    2. The default origin protocol used by CDN is HTTP, but the origin server supports only HTTPS.
    3. The origin protocol used by CDN is HTTPS, but the origin server supports only HTTP.

    Solution: Modify the CDN configuration to match the access protocol supported by the origin server. The default origin protocol used by CDN is HTTP. Change it to a protocol supported by the origin server. For details, see Origin Protocol.

  3. If the status code 502 is returned, locate the fault as follows:
    • Check whether security policies, such as Safedog and firewall, are configured on the origin server to block CDN origin IP addresses.
      • During origin pull, CDN intelligently schedules PoPs to access your origin server, and the IP addresses of the PoPs are not fixed. Configuring fixed PoP IP addresses in origin pull policies may cause origin pull failures.
      • If protection software such as Safedog is required, adjust security policies to avoid incorrect interception.
  4. If the fault persists, submit a service ticket.

Kami menggunakan cookie untuk meningkatkan kualitas situs kami dan pengalaman Anda. Dengan melanjutkan penelusuran di situs kami berarti Anda menerima kebijakan cookie kami. Cari tahu selengkapnya

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback