Troubleshooting in Cloud CDN

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)The CDN responds to file requests with 3xx codes (redirect)

Check that the resource settings include:

• Protocol used by the origins as the primary one (HTTP or HTTPS). If origins redirect requests from a URI with the http scheme to a URI with the https scheme, you must select the HTTPS protocol for the resource, and vice versa.

• Value of the HTTP Host header from which origins do not redirect requests.

  For example, if the header value is configured as www.example.com, and the origins redirect requests with this value to example.com, change the value in the settings to example.com.

The CDN responds to file requests with 4xx codes (client error)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)The CDN responds to file requests with 5xx codes (server error)

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 are not applied to the resourceUpdated settings are not 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 usersA 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 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.

Unable to configure the TLS certificateUnable to configure the TLS certificate

Certificates from Yandex Certificate Manager are supported. You can issue a new Let's Encrypt® certificate or upload one of your own.

The certificate must be located in the same folder as your CDN resource.

Below is an example of a CLI error you receive when the certificate and the CDN resource are located in different folders:

ERROR: operation (id=bcdb6qaiw8mb********) failed: rpc error: code = InvalidArgument desc = folder ids of user and certificate don't match; operation-id: bcdb6qaiw8mb********