HTTP 5xx codes can be caused by an error on an origin server or CDN edge servers.
If you have noticed a significant increase of 5xx codes or received multiple complaints from users, we recommend checking our Status Page for incidents or maintenance associated with the following services:
Make sure that your origin server is available.
If the origin is not responding, or it is returning an HTTP error, contact your hosting provider or server’s administrator to solve this issue.
curl -i -X GET https://api.gcore.com/cdn/public-ip-list
Note: We constantly update this list and suggest you two solutions: creating a script to keep the origin whitelist regularly updated or using the HTTP header authorization. Find more about ACL in the article.
HTTP 5xx errors can be caused by incorrect CDN resource's settings. Check the list of the most common errors below.
Check the origin pull protocol in the resource’s settings and make sure that your origin server uses the same protocol. For more information about this feature, refer the article.
If you use Cloudflare or CloudFront services as an origin server, select "HTTP" as the origin pull protocol. If your origin only supports HTTPS, or it has a redirect from HTTP to HTTPS, contact our Technical Support (email@example.com) to add settings.
Check the "Change Host Header" option. Make sure that the option is active, and the value is the same as the Origin Source or match with the host that you have set up on the Origin. For more information about Host Header, refer here.
To track the amount of 5xx errors use the Response codes statistic on the Report tab.
To receive detailed data about error responses, use our paid feature Raw Logs. Check the article to know more about Raw logs receiving set up and logs’ fields specifications.
Was this article helpful?
Learn more about our next-gen CDN