Web Technician OnlineWhat does this mean?
A WordPress redirect loop often involves conflicting public site URLs, HTTPS detection or rules in multiple layers. A login-only loop can also involve cookies or authentication settings. Distinguish those cases before making a database or server change.
What should I check first?
Try a private window and record the redirect sequence in the browser’s Network panel. Check whether the loop is HTTP versus HTTPS, www versus root or between login paths. Record the first repeated address, including its path and query string.
How can I diagnose the cause?
Compare WordPress Address and Site Address with the intended installation arrangement. They are not always identical for a site installed in a subdirectory. Review hosting and CDN redirects and ask how a trusted proxy communicates the original scheme to the application.
How do I fix it safely?
Back up configuration and the database before correcting the specific conflict. Use the host’s supported proxy arrangement rather than accepting arbitrary forwarded headers. If you cannot access admin, follow documented recovery controls to correct the intended URL; do not perform a blind search-and-replace across the database.
Verify the fix and know when to contact your provider
Retest public pages, login and a deep permalink using both hostnames and schemes. Remove only confirmed conflicting rules and clear relevant caches after the correction. Ask the host for help when edge and origin settings disagree, providing the hop sequence and expected public URL.
Work through these checks in order
- Capture the first repeated URL in the Network panel and decide whether the loop is a host, scheme or login-path conflict. A private-window comparison can separate account-specific cookie trouble.
- Confirm the intended WordPress Address and Site Address, especially for a subdirectory installation. Compare them with edge redirects and the host’s trusted-proxy HTTPS arrangement before editing anything.
- After backing up and correcting the specific conflict, test login and a deep permalink from both hostnames and schemes. Clear only relevant caches and preserve the path through the final canonical redirect.
Which tool can help?
DNS tools show one resolver’s public answers. Record explainers do not authenticate a message, and calculators do not monitor a server. Use the evidence alongside your provider’s logs.