Fix the broken HTTPS redirect chain on WordPress
Why it matters
Requests to the HTTPS site loop, bounce through too many redirects or get no answer, so visitors see an error instead of the site. This usually comes from two layers redirecting against each other, or from a server that accepts TLS but has no site set up for this name.
The fix
- Compare WordPress Address and Site Address (Settings, General) with the host and scheme your server or CDN redirects to. If WordPress wants www and the server wants the apex, or WordPress wants http and the server forces https, they loop.
- Use one place for redirects: disable redirect options in SSL or redirect plugins when the server or CDN already redirects. Behind Cloudflare, avoid Flexible mode.
Related
- Reported by the HTTP to HTTPS redirect check
- Serve the site over HTTPS
- Stop redirecting HTTPS to HTTP
- Redirect HTTP to HTTPS
- Shorten the redirect chain
- Fix the HTTP redirect chain
- Redirect HTTP straight to HTTPS
- Answer HTTP with a redirect to HTTPS
- Redirect www and apex to one host
- Make the www or apex name work over HTTPS
Scan your domain to see whether this applies to you.