All Products
Search
Document Center

Troubleshooting for website access failure after CDN acceleration

Last Updated: Apr 09, 2020

Overview

This article describes the troubleshooting steps for website access failure after CDN acceleration.

Detailed information

If error codes 403 and 503 are returned after CDN is enabled, you can perform the following operations to resolve the issue.

If the problem persists, you can perform the following operations to troubleshoot the problem. This article takes www.a.com acceleration domain name as an example.

  1. Check whether CDN is enabled for the domain.
    1. Run the ping command to test the network connectivity to the cdn domain name. kunlun*.com the CNAME of the suffix. If so, both the CNAME record and the accelerated domain have taken effect. For the specific verification method, see how to verify whether a CDN node takes effect.
    2. If the IP address is still the origin server IP address of the domain name in the ping command test result, this indicates that the domain name acceleration has not taken effect. Please check configure domain name-based acceleration.
  2. Determine whether the back-to-source is normal. If the domain is verified to be resolved to CDN in step 1, you only need to enter a URL under the domain name in the address bar of your browser to check the access effect after CDN acceleration.
  3. Modify the hosts file. For the Host configuration, see domain name binding Host Operation steps. Add" 12.12.12.1 2 www.a.com"Once the entry is saved, clear and reopen the browser cache. Re-access indicates a back-to-source access.
    Description: 12.12.12.12 for the source IP address, www.a.com is the domain name to be checked. 
    • If the access is still abnormal, it indicates that the access to the source site is abnormal, please directly request the source site service.
    • If the back-to-origin function is normal and an error occurs after passing through CDN, continue troubleshooting.
  4. Check whether the CDN configuration is correct. Log on to the CDN console. By www.a.com check the configuration of the domain name to check whether the CNAME matches correctly.
    Description: the origin server on the CDN console is the IP address of the corresponding origin server. No matter whether you set an IP address or a domain name here, it is resolved into the corresponding domain name for back-to-origin. The origin site is determined by the Origin Host. Therefore, the origin Host must correspond to the origin site that provides external services.

    Note: www.a.com the CNAME generated in iot platform can only www.a.com you cannot provide this service to other domain names. Ru img.a.com the domain name errors are as follows: img.a.com the CNAME must be img.a.com at the beginning.
  5. Check Origin site configuration. Log on to the CDN console. On the basic settings page, check whether the origin server of the domain name is configured as the origin. If not, change the origin information to the IP address of the corresponding server.
  6. Check the security policies of the origin. If the preceding configurations are correct, CDN is configured properly. Check whether you have configured some security policies on the origin server, such as a firewall or a dongle. If you have configured a security policy, check whether there is an IP interception record for the following four IP segments. If you have an interception record, add a whitelist.
    140.205.127.0/25 140.205.253.128/25139.196.128.128/25 101.200.101.0/25

Applicable to

  • CDN