Too many redirects
Symptoms
- The browser shows "too many redirects" or "redirect loop".
- The page never loads, and the address keeps changing.
- The problem started after enabling HTTPS, changing nameservers, or editing redirect rules.
Common causes
- Forced HTTPS is enabled in two places, for example in the hosting settings and in the application.
- The
.htaccessfile or a CMS plugin redirects tohttps://while the site already redirects from it. - The site URL in an application does not match the address you visit, such as
wwwagainst the bare domain. - A proxy or CDN sends visitors to
https://on every request.
Safe initial checks
- Watch the redirect chain. Use the browser's network tools, or run
curl -I https://yourdomain.comand look at eachLocationheader. - Test in a private window to rule out cached redirects.
- List every redirect source: the hosting settings, the
.htaccessfile, and the application settings.
Copy any file before you edit it.
Step-by-step solutions
- Duplicate HTTPS redirect. Keep the redirect in one place only. See SSL and HTTPS settings.
- Conflicting
.htaccessrule. Remove the duplicate rule, and keep one rule forhttp://tohttps://. - Mismatched site address. Set the application's site address to the exact address visitors use, with or without
www. - Proxy or CDN. Set the proxy to pass the original protocol, so the application does not redirect again.
How to confirm the issue is fixed
curl -I http://yourdomain.comshows one redirect to the final address, and the final address returns status 200.- The page loads in a private window.
When to contact support
Contact support if the redirect comes from the hosting server and you cannot find the source in your settings.
Information to include in a support ticket
- The address you visited, and the redirect chain from
curl -I. - The changes you made just before the problem started.
Related articles
Last reviewed
2026-10-27
