iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To troubleshoot a website error while Hostinger CDN is enabled, first confirm the failing response actually passed through Hostinger CDN. Then use the error code and two controlled comparisons—Development mode and, if needed, temporarily disabling the CDN—to tell a cache or CDN-path issue from an application, hosting, or DNS problem.
First, confirm the request went through Hostinger CDN
- Reproduce the failure in your browser and open Developer Tools. In the Network panel, select the failed request and inspect its response headers.
- Look for
x-hcdn-request-id. Hostinger says this header appears on responses delivered through its CDN. If it is absent, the request may have gone directly to the site or through another proxy, so do not assume Hostinger CDN handled it. - If the header is present, save its full value. Hostinger support can use the request ID to investigate the specific request.
- Check
x-hcdn-cache-status, if present. Hostinger listsHIT,MISS,EXPIRED,DYNAMIC,BYPASS, andREVALIDATEDas possible values. These describe cache handling; by themselves, they do not prove the cache caused the error.
Hostinger says its CDN does not cache error responses, so an error response is not necessarily a stale cached error. Fixing the underlying issue can make the error disappear for visitors without a cache change. See Hostinger Help Center’s website error troubleshooting guide.
Use the error code to choose what to inspect
403 Forbidden: check traffic and security rules
Review Hostinger CDN traffic-blocking rules for IP-address or country blocks, and check whether the security level is blocking legitimate visitors. If the error affects a form, login, REST API call, page-builder AJAX request, or payment callback, inspect that exact failed request and the rules and security setting that apply to it. Hostinger also has guidance on fixing blocked legitimate requests.
408 and 504: distinguish a slow visitor connection from a slow site
Hostinger describes a 408 as a visitor connection that was too slow to complete the request. A 504 means the website did not respond before the CDN stopped waiting. For a 504, check hosting resource usage and consider whether a recently added plugin or a heavy page builder is contributing to the slow response.
#1 Best Overall
500 Internal Server Error: investigate the application
Hostinger says a 500 usually comes from the website application. Check error logs and review recent code or plugin changes. An application-caused 500 should also appear when the CDN is disabled, which makes the route comparison below useful.
502 and 503: check whether the interruption is temporary
Hostinger describes 502 and 503 errors as signs that the website may be temporarily unreachable or overloaded. They can clear within minutes. If the error persists, continue with the isolation steps rather than treating a brief interruption as proof of a CDN fault.
More broadly, Hostinger lists code problems, plugin or theme overload or logical errors, and exhausted hosting resources as possible causes of 5xx errors. Its general advice also includes ruling out local cache and trying another network or device. See its 5xx error guidance.
Test whether the CDN cache is involved
Use Hostinger CDN’s Development mode as a diagnostic comparison. Hostinger says this mode makes the CDN fetch each request directly from the website while bypassing the CDN cache.
- Turn on Development mode using the Hostinger controls for your CDN.
- Repeat the same action that produced the error, using the same URL and request type where possible.
- If the error disappears, flush the CDN cache and turn Development mode off.
- If the error remains, clear other relevant cache layers, such as LiteSpeed server cache or a WordPress caching plugin, before concluding that the application itself is responsible.
Development mode is an isolation step, not a repair for a slow origin, broken plugin, or application error.
Compare the site with Hostinger CDN temporarily disabled
If the cache test does not isolate the issue, temporarily disable Hostinger CDN and allow a few minutes for DNS changes to take effect. Then reproduce the same failure.
- Error remains with CDN disabled: Investigate the website or hosting environment. Check application logs and hosting resource use, especially for 500 or persistent 504 errors.
- Error occurs only with CDN enabled: Re-enable the CDN and contact Hostinger support with the failing URL, the time of the error, and the full
x-hcdn-request-id, if available.
Do not treat the first result immediately after a DNS change as conclusive: some visitors may still reach the CDN or see a placeholder while DNS caches expire.
Recommended Free Tools
Check redirect loops, DNS, and certificate errors
Redirect loop
Hostinger identifies two common causes: another active proxy, such as Cloudflare, and conflicting manual redirects in .htaccess or WordPress settings. Hostinger recommends using only one CDN for a site. Check redirect rules individually so you can identify which setting creates the loop.
DNS changes and CDN routing
Hostinger says the domain must use Hostinger nameservers for its CDN. When the CDN is enabled, it routes the root A/AAAA records and the www record to the CDN and manages those records. Disable the CDN before changing the root or www records. See Hostinger Help Center’s Hostinger CDN and DNS records guide.
After disabling the CDN, DNS caches usually expire within hours, according to Hostinger, but that is not a guaranteed time for every visitor or network. Hostinger advises contacting support if the site remains unreachable more than 24 hours after enabling or disabling the CDN.
Certificate error
Hostinger says its CDN serves certificates for the root and www hostnames. If a certificate error affects www, check that it uses the Hostinger-managed CNAME.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11What to include when contacting Hostinger support
- The complete URL that fails and the exact error shown.
- The time the error occurred.
- The full
x-hcdn-request-id, if the response includes it. - Whether the error persists in Development mode and with the CDN disabled.
- Which caches you cleared, and any relevant application-log or hosting-resource findings.
This information helps distinguish a request handled by Hostinger CDN from one that reached the site directly or through another proxy.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
