Why does a redirect loop appear after enabling HTTPS?

A redirect loop means two or more rules keep sending the request between addresses. One layer may force HTTPS while another believes the original request was HTTP and sends it back through the same rule. Conflicting redirects between www and the root domain can create a similar cycle.

This is common when a CDN, reverse proxy, or load balancer terminates HTTPS before forwarding the request to the origin server. The application needs the correct forwarded-protocol information, and the proxy’s SSL mode must match the origin setup. A flexible mode combined with an origin rule that forces HTTPS is a frequent source of loops.

Trace the response headers with a redirect checker or command-line HTTP client. List each location in order and identify which layer returned it. Review CDN rules, hosting redirects, .htaccess or web-server configuration, WordPress URL settings, and redirection plugins. Disable or edit one layer at a time.

Choose one canonical HTTPS hostname and make every source address lead toward it. Keep the origin certificate valid when the proxy connects over HTTPS. After correcting the rules, purge caches and test in a private window because browsers can remember permanent redirects even after the server configuration changes.