- \n
- Confirm that Hostinger CDN is enabled<\/a> for the affected website. Go to hPanel → Websites<\/strong>, click Dashboard<\/strong> next to the website, and check the status under Performance → CDN<\/strong>. For Agency hosting, select CDN directly on the left sidebar.<\/li>\n
- Hostinger CDN does not cache error responses, so fixing the underlying issue makes the error disappear for visitors immediately.<\/li>\n<\/ul>
Identify whether the error comes from Hostinger CDN or your website<\/h2>
Every response delivered through Hostinger CDN includes the
`x-hcdn-request-id`<\/code> response header. To check it:<\/p>- \n
- Open the failing page in a browser.<\/li>\n
- Open the browser developer tools (F12) and select the Network<\/strong> tab.<\/li>\n
- Reload the page and click the first request in the list.<\/li>\n
- Check the Response Headers<\/strong> section.\n
- \n
- If the
`x-hcdn-request-id`<\/code> header is present, the response was delivered through Hostinger CDN. The header value identifies the exact request, for example`7f3a1c...-us-phx-edge2`<\/code>.<\/li>\n- If the header is missing, the request did not go through Hostinger CDN. In that case, the error comes directly from the website or from another proxy service, such as Cloudflare.<\/li>\n<\/ul>\n<\/li>\n<\/ol>
The
`x-hcdn-cache-status`<\/code> header shows how the CDN handled the content: HIT<\/strong> (served from cache), MISS<\/strong> (fetched from your website), EXPIRED<\/strong> (cached copy expired and fetched again), DYNAMIC<\/strong> (not cacheable), BYPASS<\/strong> (cache skipped), or REVALIDATED<\/strong> (refreshed content).<\/p>NOTE<\/strong><\/p>
- \n
- Copy the full
`x-hcdn-request-id`<\/code> value when reporting a problem. The request ID lets Hostinger locate the exact request in the logs.<\/li>\n<\/ul>Fix common HTTP errors with Hostinger CDN<\/h2>
There are five common error groups on websites using Hostinger CDN: 403, 408, 500, 502\/503, and 504.<\/p>
403 Forbidden with Hostinger CDN<\/h3>
A 403 error<\/a> from Hostinger CDN usually means the request was blocked by a security feature. Check these settings in the CDN dashboard:<\/p>
- \n
- Open Performance<\/strong> → CDN<\/strong> and click Manage<\/strong>.
\n![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/08\/2026-08-20_09-21.png\")
<\/li>\n- In the Traffic blocking<\/strong> tab, review IP<\/strong> <\/a>and country<\/strong> <\/a>blocking rules. Remove rules that cover your visitors or services.<\/li>\n
- In the Security<\/strong> tab, try a lower security level<\/strong><\/a> if legitimate visitors are blocked.<\/li>\n<\/ol>
Follow the guide Hostinger CDN: How to fix blocked legitimate requests<\/a> if forms, logins, or API requests return 403.<\/p>
408 and 504 timeout errors with Hostinger CDN<\/h3>
A 504 error means your website did not respond in time, and the CDN gave up waiting. Common causes are slow database queries, heavy plugins, or exhausted PHP workers on the hosting plan. A 408 error is different: the visitor’s connection was too slow to deliver the complete request, which usually indicates a network issue on the visitor’s side. For 504 errors:<\/p>
- \n
- Check your hosting resource usage<\/a> in hPanel → Websites → Dashboard → Performance.<\/strong><\/li>\n
- Temporarily deactivate recently added WordPress plugins<\/a> or heavy page builders.<\/li>\n
- Retry the page after each change.<\/li>\n<\/ol>
500 Internal Server Error with Hostinger CDN<\/h3>
A 500 error<\/a> usually comes from the website application, and Hostinger CDN forwards it to the visitor. Check the website error logs and recent code or plugin changes. An application-caused 500 error also appears with the CDN disabled, which the isolation steps below confirm.<\/p>
502 and 503 errors with Hostinger CDN<\/h3>
502 and 503 errors<\/a> indicate that your website was temporarily unreachable or overloaded. These errors often resolve on their own within minutes. If a 502 or 503 error persists, continue with the isolation steps below.<\/p>
Isolate the cause with Development mode<\/h2>
Development mode makes Hostinger CDN fetch every request directly from your website, skipping the cache:<\/p>
- \n
- Go to hPanel → Websites → Dashboard → Performance → CDN<\/strong>.
\n![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/08\/2026-08-20_08-28.png\")
<\/li>\n- Enable Development mode<\/strong>.
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/08\/2026-08-20_09-22.png\")
<\/li>\n- Reload the failing page in an incognito browser window.<\/li>\n<\/ol>
If the error disappears, flush the CDN cache<\/a>: click Flush cache<\/strong> in the CDN section, then disable Development mode<\/strong>.
\n![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/08\/2026-08-20_09-39.png\")
\nIf the error persists in Development mode<\/strong>, clear the remaining cache layers — the LiteSpeed server cache in Cache Manager<\/a> and any WordPress caching plugin — before concluding that the website application is at fault. Development mode affects Hostinger CDN caching only.<\/p>Temporarily disable Hostinger CDN to confirm the source<\/h2>
Disabling the CDN entirely removes it from the equation:<\/p>
- \n
- Go to hPanel → Websites → Dashboard → Performance → CDN.
\n
\n<\/strong><\/li>\n- Click Disable<\/strong>.
\n![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/08\/2026-08-20_09-21_1.png\")
<\/li>\n- Wait a few minutes for DNS changes to take effect, then test the page again.<\/li>\n<\/ol>
If the error still appears with Hostinger CDN disabled, the cause is the website or hosting environment. If the error only appears with the CDN enabled, re-enable it and contact Hostinger support with the URL, the time of the error, and the
`x-hcdn-request-id`<\/code> value from the failing response.<\/p>Fix redirect loops with Hostinger CDN<\/h2>
- Click Disable<\/strong>.
- Enable Development mode<\/strong>.
- Temporarily deactivate recently added WordPress plugins<\/a> or heavy page builders.<\/li>\n
- In the Traffic blocking<\/strong> tab, review IP<\/strong> <\/a>and country<\/strong> <\/a>blocking rules. Remove rules that cover your visitors or services.<\/li>\n
- Open Performance<\/strong> → CDN<\/strong> and click Manage<\/strong>.
- If the header is missing, the request did not go through Hostinger CDN. In that case, the error comes directly from the website or from another proxy service, such as Cloudflare.<\/li>\n<\/ul>\n<\/li>\n<\/ol>
- Hostinger CDN does not cache error responses, so fixing the underlying issue makes the error disappear for visitors immediately.<\/li>\n<\/ul>