Why Is My Domain Name Inaccessible After HTTPS Secure Acceleration Is Configured?
Possible cause: The origin protocol of the domain name is HTTP and force redirect from HTTP to HTTPS is configured on your origin server, so that the domain name cannot be accessed using HTTP or HTTPS.
In this case, a status code 301 is returned. CDN points of presence (PoPs) access the origin server using HTTP rather than HTTPS until the maximum number of retransmissions has been reached. As a result, the access will fail.
Solution: Go to the CDN console, choose Domains in the navigation pane, click Configure in the Operation column, click the Origin Settings tab, and set Origin Protocol to Same as user.
Troubleshooting FAQs
- Why Am I Seeing a Message Indicating that the Domain Name Already Exists When I Add a Domain Name for CDN Acceleration?
- Why Is My Domain Name Inaccessible After HTTPS Secure Acceleration Is Configured?
- Why Is Data Obtained from a CDN PoP Not the Updated Data?
- Why Is 304 Returned When a User Accesses a Resource Under My Acceleration Domain Name?
- Why Is the Accelerated Page Incorrect Even Though I Can Access the Origin Server?
- Why Can't a Web Page Be Properly Displayed After the Origin Server's IP Address Is Changed?
- Why Do I Get an Access Failure and Access-Control-Allow-Origin Error?
- Why Does the System Always Display "301" After HTTPS Is Configured for a Domain Name?
- Why Do I Get Request Timed Out When Trying to Ping an Acceleration Domain Name?
- Why Are Incorrect Resources Being Pulled from My Origin Server?
- Why Is My Site Slow the First Time I Access It After CDN Is Configured?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
more