WordPress
WordPress SSL redirect: how to fix redirect loops
An HTTPS redirect loop means two or more layers disagree about the canonical URL or whether the request is already secure. WordPress may be correct on its own while a proxy, CDN, web server, or plugin keeps sending the browser back to a previous state.
Capture the redirect chain
Use browser developer tools or an HTTP client to see each response and Location header. Identify whether the loop alternates between HTTP and HTTPS, www and non-www, or two application paths.
Check WordPress site URLs
The WordPress Address and Site Address should reflect the intended public URL unless the architecture deliberately requires something else. Database constants or environment-specific configuration can override dashboard values.
Make proxies communicate the original scheme correctly
When TLS terminates at a reverse proxy or CDN, the application still needs reliable information that the visitor used HTTPS. If WordPress thinks every proxied request arrived over HTTP, it may redirect an already-secure request again.
Avoid stacking several independent redirect systems
A CDN rule, web-server rule, WordPress plugin, and application setting can all try to enforce HTTPS. Choose a clear canonicalization layer and remove redundant rules after the desired path is verified.