A 508 error can mean two different things. The website may be stuck going around in a circle, or the hosting account may have used all of an allocated resource.
The wording on the error page matters. "Loop Detected" or "too many redirects" points to conflicting website rules. "Resource Limit Is Reached" points to hosting capacity or an unusually heavy workload.
This article is part of our Common Web Server Errors Explained series.
The short version
If the page mentions a loop, look for conflicting HTTPS, domain or WordPress redirect settings. If it mentions a resource limit, check which hosting resource was exhausted and what the website was doing at the time.
These are different problems that happen to share the number 508. Read the full error message before choosing a fix.
In the formal web standard, 508 was introduced for loops encountered while managing files through a system called WebDAV. Some hosting platforms also use the same number for Resource Limit Is Reached.
What does a 508 Loop Detected error mean?
A website request can be transformed several times before content is returned. HTTP may redirect to HTTPS, a non-www domain may redirect to www, a CDN may forward traffic to an origin and WordPress may apply its own canonical URL rules.
Each transformation can be valid on its own. A loop appears when the layers disagree about the final destination.
For example, a CDN may connect to the origin over HTTP while telling visitors to use HTTPS. If the origin does not recognise that the original request was secure, it redirects back to HTTPS. The CDN makes another HTTP origin request, and the cycle repeats.
This differs from a 404 Not Found, where routing reaches no valid resource, and from 403 Forbidden, where a policy deliberately refuses access.
The server, browser or proxy eventually stops the sequence and returns an error rather than follow it forever.
508 can also mean Resource Limit Is Reached
On shared hosting platforms, particularly those using account-level resource controls, a 508 page can mean the hosting account has reached an allocated limit. This is not the same as the standards-based WebDAV loop response, even though it uses the same status number.
The limit might involve CPU, memory, concurrent web processes, entry processes or another account-level resource. Once the threshold is reached, the platform temporarily refuses additional work so one busy or faulty account cannot affect every other customer on the server.
The visible symptom may be intermittent. A site can load normally, return 508 during a burst of traffic and recover once existing requests finish. That pattern often points towards capacity or request concurrency rather than a redirect loop.
Reaching a resource limit does not automatically mean the hosting plan is too small. The extra load might be legitimate growth, but it can also come from bots, an inefficient plugin, a stuck background task, slow database queries or uncached traffic. Upgrading the plan without understanding the workload may only postpone the same problem.
The hosting account's resource history and server logs should show which limit was reached and when. Compare those timestamps with traffic, scheduled tasks, WordPress activity and recent changes. If legitimate demand has outgrown the available capacity, an upgrade may be appropriate. If one plugin or bot is consuming the resources, correcting or filtering that workload is usually the better first step.
Common causes of loops
Conflicting HTTP and HTTPS rules are among the most common causes. The CDN, web server and application may all try to force HTTPS using different signals.
Disagreement between www.example.com and example.com can create another cycle. One layer adds www while another removes it.
WordPress stores a WordPress Address and Site Address. If those values conflict with the public domain, hosting proxy or migration settings, WordPress may continually redirect to what it believes is the canonical URL-the preferred official address for the site.
Redirect plugins can overlap with .htaccess, NGINX or CDN rules. An old migration redirect may remain active after a new domain rule is introduced.
Authentication and cookie logic can loop as well. A protected page sends a user to login, but a caching or role issue sends the authenticated user back to the protected page without recognising the session.
Multilingual, ecommerce and membership plugins add complex routing that can conflict with canonical redirects. At the server level, recursive rewrite rules can repeatedly transform the same path.
In hosting environments, a 508 may therefore indicate a redirect or processing loop, or that an account-level resource limit has been reached. The error page, account metrics, server logs and platform documentation will clarify how the code is being used.
How to diagnose a 508 or redirect loop
Start by recording the complete redirect chain. Browser developer tools, command-line HTTP clients and redirect-checking tools can show each status code and Location header.
Look for the first repeated URL or state. A sequence that alternates between HTTP and HTTPS points towards protocol awareness. One that alternates between www and non-www points towards canonical host rules. A loop between login and account pages suggests application state or cookies.
Test the origin and CDN separately where safe. Compare headers reaching the application, including Host and forwarded protocol headers. Reverse proxies must communicate the original scheme correctly, and the application must trust those headers only from approved proxies.
Review rules at every layer: registrar forwarding, CDN redirects, load balancer configuration, Apache or NGINX, .htaccess, WordPress URL values and redirect plugins. A loop often exists because nobody has a complete view of all of them.
Check what changed immediately before the issue began. Enabling a CDN, forcing HTTPS, changing domains, installing a security plugin or completing a migration are strong leads.
Clear browser and edge caches only after documenting the chain. A cached permanent redirect can make a corrected configuration look broken for longer.
How to fix a redirect loop
Choose one official website address. Decide whether it uses HTTPS with or without www, then make every layer agree.
Apply each redirect once and as early as practical. If the CDN handles HTTP-to-HTTPS and hostname canonicalisation reliably, the origin should understand and preserve that decision rather than contradict it.
Correct proxy headers and application trust settings so WordPress or another framework recognises the original request as secure. Never trust forwarded headers from arbitrary internet clients; restrict that trust to the actual proxy network.
Remove duplicate, obsolete and contradictory redirect rules. Preserve a copy before changing .htaccess, NGINX or CDN configuration, and test one change at a time.
For login loops, exclude authentication and account pages from full-page caching, verify cookie domains and confirm application URLs. Sign out and clear site-specific cookies after fixing the configuration.
Avoid switching off HTTPS or security controls as a permanent workaround. The goal is consistent routing, not weaker protection.
508 and redirect loops in WordPress
WordPress is particularly sensitive to its stored URLs and proxy environment. The home and siteurl values must reflect the intended architecture, while constants in wp-config.php can override database settings.
After a migration, old domains can remain in plugin settings or redirect tables. WordPress stores some settings in a special database format, so careless search-and-replace edits can damage them and introduce new problems.
Caching plugins may force HTTPS or canonical hosts, while security plugins can change login URLs and access behaviour. WooCommerce and membership plugins add account redirects that depend on sessions and cookies.
If the dashboard is inaccessible, an experienced administrator can inspect URL values through the hosting tools, WP-CLI or database. Make a backup before changes and remove temporary overrides once the correct settings are restored.
Test the public site, administration area, login, logout, checkout and account pages after fixing the loop. Different paths can use different redirect logic.
Is a 508 a hosting issue or an application issue?
It depends on which rules conflict.
Your hosting provider is responsible for proxy behaviour, server rewrites, TLS termination and platform-level redirects. They should be able to provide request logs and confirm the headers passed to the application.
The website owner or developer is responsible for WordPress URL settings, redirect plugins, application routes and custom authentication logic. CDN configuration may belong to either party.
Loops are often shared configuration problems rather than a clean failure on one side. A hosting change can be correct in isolation while exposing an old application assumption. The fastest resolution comes from mapping all layers together.
How to prevent future loops
Document the canonical domain, HTTPS policy and the layer responsible for each redirect. Avoid implementing the same policy independently in a CDN, server and plugin unless there is a clear reason.
Test redirect chains after domain, CDN, proxy, SSL and migration changes. Include deep links, login, logout and checkout rather than checking the homepage alone.
Keep redirect rules under change control, review old rules and avoid long chains. Use temporary 302 redirects while testing major changes, then move to 301 only when the destination is confirmed.
Monitor for sudden increases in 3xx and 508 responses. Retain logs from both edge and origin services so intermittent loops can be reconstructed.
For WordPress, use staging for URL and routing changes, back up the database and understand which settings are controlled by the application, plugin and hosting layer.
Frequently asked questions
Is 508 the same as "too many redirects"?
It can be. Browsers commonly show "too many redirects" while servers or hosting platforms may return 508 for a loop. A 508 Resource Limit Is Reached page is a different hosting-platform use of the same number and needs a resource investigation instead.
What does "508 Resource Limit Is Reached" mean?
It means the hosting account has temporarily reached a resource threshold such as CPU, memory or concurrent processes. Review the account's resource history and the workload at that time before deciding whether to optimise the site, block unwanted traffic or upgrade the hosting plan.
Can clearing cookies fix a redirect loop?
It can fix a user-specific login or session loop. It will not correct contradictory server or CDN rules. Clear site-specific data after the configuration is fixed.
Can Cloudflare cause a redirect loop?
A loop can occur when Cloudflare's SSL or redirect settings conflict with the origin. The issue is the mismatch between layers rather than Cloudflare alone.
Why did the loop start after enabling HTTPS?
The proxy may terminate HTTPS but contact the origin over HTTP. If the origin does not recognise the forwarded scheme, it redirects every request back to HTTPS.
Can a WordPress plugin cause 508?
Yes. Redirect, security, multilingual, caching and membership plugins can create or contribute to loops, particularly when overlapping with server rules.
Does a redirect loop affect SEO?
Yes. Search engines and visitors cannot reach the final content. Correct the loop promptly and keep canonical redirects short and consistent.
Final thoughts
A 508 or "too many redirects" error is usually the result of individually reasonable rules that disagree with one another.
The solution is not another redirect. It is a clear decision about the final URL and which layer owns each transformation on the way there.
At Network Dynamics, our engineers can help diagnose the error, explain the cause in plain English and recommend a practical next step. You will not be left wondering whether the 508 comes from a redirect loop, WordPress, a CDN rule or an exhausted hosting resource-or whether the right solution is a configuration change, application work or additional capacity.
Return to Common Web Server Errors Explained, or revisit the start of the series with What Is a 401 Unauthorised Error?.
