On this page

Show all

Help Center/ Content Delivery Network/ FAQs/ Troubleshooting/ Why Is My Domain Name Inaccessible After HTTPS Secure Acceleration Is Configured?

Why Is My Domain Name Inaccessible After HTTPS Secure Acceleration Is Configured?

Updated on 2024-04-17 GMT+08:00

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.

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback