Troubleshooting in Cloud CDN
- The CDN responds to file requests with 3xx codes (redirect)
- The CDN responds to file requests with 4xx codes (client error)
- The CDN responds to file requests with 5xx codes (server error)
- Updated settings aren't applied to the resource
- A CDN resource has the Not active status and content is not available to users
Below is the list of the most frequent issues with Cloud CDN and ways to resolve them.
The CDN responds to file requests with 3xx codes (redirect)
Check that the resource settings include:
-
The protocol used by the origins as the primary protocol (HTTP or HTTPS). If origins redirect requests from a URI with the
http
scheme to a URI with thehttps
scheme, you must select the HTTPS protocol for the resource, and vice versa. -
The value of the HTTP
Host
header from which origins don't redirect requests.For example, if the header value is configured as
www.example.com
, and the origins redirect requests with this value toexample.com
, change the value in the settings toexample.com
.
The CDN responds to file requests with 4xx codes (client error)
Make sure that:
-
End-client access to the content is allowed in the resource settings.
-
Origins return files in response to direct requests (bypassing the CDN).
-
Origins allow and correctly process requests that match the resource settings:
- Over the specified protocol: HTTP or HTTPS.
- With the specified value of the
Host
HTTP header and other headers.
The CDN responds to file requests with 5xx codes (server error)
Note
CDN servers do not support IPv6 and can only access sources via IPv4 addresses.
Make sure that:
-
Origins respond to CDN server requests within 5 seconds.
-
Origins allow and correctly process requests that match the resource settings:
- Over the specified protocol: HTTP or HTTPS.
- With the specified value of the
Host
HTTP header and other headers.
Also check the Cloud CDN status on the Yandex Cloud special page
Updated settings aren't applied to the resource
It may take up to 15 minutes for the new settings of the existing resource to apply to CDN servers. After that, we recommend purging the resource cache.
A CDN resource has the Not active status and content is not available to users
Resources may have the Not active
status due to receiving no user requests for 90 days or to being deactivated manually. To make them active again, enable the End-user access to content option in the basic resource settings. Resources can be activated and deactivated by users with the cdn.editor
role or higher.