How to Fix Joomla Redirect Loops
Confirm the loop before changing Joomla
Open the affected URL in a private browser window or inspect it with an HTTP client that shows each redirect response. Record the sequence of URLs and status codes. A loop can come from Joomla, the web server, a CDN, a reverse proxy, or several layers redirecting the same request in different directions.
Check Joomla Force HTTPS and canonical host behavior
In System → Global Configuration → Server, review Force HTTPS. If HTTPS is already enforced by the host, load balancer, or CDN, make sure Joomla sees the original request scheme correctly. Also check whether another layer forces www while a second layer removes www, or vice versa.
Review server rewrite rules
Inspect .htaccess, Nginx, IIS, hosting-panel redirects, and virtual-host rules for overlapping HTTP-to-HTTPS, hostname, trailing-slash, or index.php redirects. Joomla's own SEF routing should not be surrounded by competing rules that continually transform the same request.
Check proxies and CDNs
When TLS terminates at a proxy or CDN, the origin may receive an HTTP connection even though the visitor used HTTPS. If the proxy headers or trusted-proxy configuration are wrong, Joomla or the origin server can believe the request is insecure and redirect back to HTTPS repeatedly. Verify the provider's documented forwarding configuration.
Disable one redirect layer at a time
On staging or during a controlled maintenance window, temporarily remove the most likely duplicate redirect rule and retest the complete chain. Do not disable all security controls at once. The goal is to identify which two rules disagree, then keep one clear canonicalization strategy.
Clear caches after correcting the rule
Browsers can cache permanent redirects, while CDNs and Joomla caching can preserve old responses. Purge only the relevant caches and retest in a fresh session. If a previous 301 is cached locally, an HTTP inspection tool can help distinguish the current server response from browser history.
Verify important routes after the loop is gone
Test the home page, Administrator, login, article and category URLs, media files, and any checkout or account paths. Confirm HTTP resolves to the intended HTTPS canonical URL in a short chain and that unknown URLs still return the correct error instead of being redirected indiscriminately.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.