How to Fix an HTTPS Redirect Loop in Joomla
An HTTPS redirect loop usually means two layers disagree about whether the original visitor connection is secure or about which hostname is canonical. This is especially common when Joomla sits behind Cloudflare, another CDN, a reverse proxy, or a load balancer. Trace the redirects first, then correct the conflicting layer rather than adding another redirect.
Record the exact loop
- Use a private browser window or HTTP header tool.
- Start with the failing HTTPS URL.
- Record every status code and
Locationvalue. - Look for HTTPS-to-HTTP changes, hostname flips, port changes, or the same HTTPS URL repeating.
This separates an HTTPS-awareness problem from a general Joomla routing problem.
Check where TLS terminates
Determine whether the browser connects directly to the Joomla web server or whether a CDN/proxy terminates TLS first. If a proxy forwards the request to the origin over HTTP, the origin must have a reliable way to know the visitor originally used HTTPS. Review the host or proxy documentation for forwarded-protocol handling rather than trusting arbitrary client-supplied headers.
Remove competing HTTPS enforcement
Review CDN settings, hosting redirects, Apache/Nginx/IIS rules, Joomla HTTPS/proxy settings, and security/SEF extensions. Keep one coherent enforcement path. A classic failure is an edge that sends HTTPS traffic to an HTTP origin while the origin blindly redirects every HTTP connection to HTTPS.
Check hostname and port normalization too
An apparent HTTPS loop can actually alternate between www and non-www, or between a proxy's external port and an origin rule. Make the preferred scheme and hostname consistent across Joomla, the server, and the edge service.
Retest methodically
- Purge only relevant CDN/server caches after changing a rule.
- Test HTTP and HTTPS versions of the home page.
- Test a deep Joomla route and Administrator.
- Confirm each alternate URL reaches one final HTTPS URL without repeating.
- Review logs for unexpected redirect responses.
If HSTS is already active, remember the browser may internally upgrade HTTP before contacting the server. Use header-level testing to distinguish browser policy from server redirects.
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.