Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →A WordPress redirect loop has no single universal fix. First identify whether it affects the whole site, only login, or one route. Then compare WordPress’s configured URLs with the public URL and check for conflicting HTTPS, proxy, plugin, CDN, host, or web-server redirects.
Identify where the redirect loop occurs
Browsers may show “ERR_TOO_MANY_REDIRECTS,” “too many redirects,” or repeatedly reload a login page. Start by recording the URL you opened and, if available, the sequence of redirect destinations (the Location values). Note whether the problem affects the whole public site, only wp-login.php or wp-admin, only HTTP or HTTPS, or one page or language-prefixed path. This distinction helps narrow which settings and administrator to involve.
- Whole site: compare canonical URLs and inspect HTTPS and redirect rules across WordPress and hosting layers.
- Login only: check cookies, URL settings, and plugin conflicts.
- One route: investigate rules or behavior specific to that page, language path, plugin, or cache.
WordPress’s login troubleshooting guidance identifies URL mismatches, mixed schemes, and conflicting CDN, proxy, host, or server redirects as possible causes.
Compare WordPress’s URLs with the public URL
Choose the one canonical address visitors should use, including its scheme (https or http), host (www or non-www), and any installation subdirectory. Compare that address against both WordPress URL constants, if present, and the corresponding database options.
#1 Best Overall
- easy to use
- Free app
- Compatible with all devices
- It gives the best comparison between ten different hosts
- Open
wp-config.phpand check forWP_HOMEandWP_SITEURL. If defined, confirm both match the intended scheme, host, and installation path. - Check the database options
homeandsiteurl. Confirm they use the same intended values and are not left on an old domain or HTTP address after a migration. - Compare the values with the address visitors actually use. Look for disagreements such as HTTP versus HTTPS,
wwwversus non-www, or a missing subdirectory.
Do not change several layers at once: that makes it harder to identify which mismatch caused the loop. WordPress lists conflicting constants, incorrect database values, and mixed schemes among the checks in its login troubleshooting documentation.
Check HTTPS when a proxy handles TLS
Confirm that the public HTTPS endpoint and certificate work, then establish where TLS encryption ends. If a CDN or reverse proxy accepts HTTPS but connects to the WordPress origin over HTTP, WordPress may see an HTTP request and redirect it to HTTPS repeatedly. WordPress’s HTTPS administration handbook describes this architecture: “If WordPress is hosted behind a reverse proxy that provides SSL, but is hosted itself without SSL, these options will initially send any requests into an infinite redirect loop.”
The handbook gives an example in which WordPress recognizes the HTTP_X_FORWARDED_PROTO header. That approach depends on the proxy being correctly configured to set the header. Have the administrator verify the trusted proxy and header configuration for the actual setup; do not copy proxy-specific code blindly.
Find and remove conflicting redirect rules
Redirects can be configured at more than one layer. Review the active rules in WordPress plugins or custom code, a CDN or DNS proxy, the hosting control panel, Nginx, Apache, and any other reverse proxy. A rule that sends HTTPS back to HTTP can conflict with an HTTPS-enforcement rule; host or path canonicalization rules can conflict too. WordPress’s troubleshooting guidance names these kinds of layers as potential sources of conflicts.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →If you do not manage the CDN, proxy, hosting, or web-server configuration, ask the person who does to inspect those rules. Fix one conflicting layer at a time and check whether the affected URL now reaches its intended destination.
Troubleshoot a login-only loop
When the loop is limited to login, use WordPress’s login-loop checklist:
- Clear the site’s cookies, then try logging in again.
- Check
WP_HOMEandWP_SITEURLinwp-config.php, along with the database’shomeandsiteurlvalues. - Temporarily rename the plugins folder to test whether a plugin conflict is involved. Preserve the original folder name so you can restore it, and make this change only if you can access the site files.
If the site uses an SSL plugin, a WordPress.org support discussion about one such case suggests checking that WordPress Address and Site Address use HTTPS and re-saving permalinks. Treat that as a case-specific troubleshooting suggestion, not a guaranteed fix: it will not resolve a conflicting proxy or server rule.
Handle loops that begin after a migration
After changing a domain or moving from HTTP to HTTPS, stored links may still point to the old address. Back up the database before making replacements. WordPress recommends WP-CLI’s search-replace command and its --dry-run option to preview what would change before applying it. Follow the WordPress migration URL guidance for the procedure appropriate to your site.
Best Value
- Free WordPress Hosting Guide Android Application. It Contains: A Brief Overview of WordPress Hosting, 9 Major Benefits of Managed WordPress Hosting.
- 5 Simple Steps to Choose WordPress Hosting, How to Maximize Your WordPress Hosting and Blogging Success, How to Choose the Best WordPress Hosting Provider, Optimize Your Blog with VIP Word.
- Press Hosting, What You Should Know to Choose the Best WordPress Hosting and Much More.
Investigate a loop limited to one page or language path
If the homepage, one post, or a language-prefixed route loops while other pages work, inspect behavior specific to that route. Test relevant redirect, SEO, or language plugins; caches; and custom URL rules separately. WordPress.org support discussions include individual examples involving routes, caches, and plugins, but they do not establish one cause or fix for every site.
Re-saving permalinks may be appropriate for some route-related cases, but it is not a general remedy for scheme or proxy conflicts. Change one relevant setting at a time so you can tell whether the route behaves differently.
Quick Recap
Choose the next place to investigate
| What fails | Check first | Who may need access |
|---|---|---|
| Whole site | Canonical URL values, HTTPS handling, and duplicate redirect rules | WordPress and hosting, CDN, proxy, or server administrator |
| Login only | Site cookies, URL constants, database URL options, and plugin conflicts | WordPress site or file administrator |
| One page or language route | Route-specific plugin, cache, or custom URL behavior | WordPress site administrator |
| Started after a migration | Old URLs in settings or stored content; preview database replacements | WordPress and database administrator |
| Public HTTPS works, but origin uses HTTP behind a proxy | Proxy TLS termination and forwarded-protocol configuration | CDN, proxy, or hosting administrator |
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
