The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
If WordPress shows “ERR_TOO_MANY_REDIRECTS,” first check that the public site URL, WordPress URL, and any HTTPS or proxy rules agree. Then test cookies and plugins if the problem affects only login. Redirect loops can also be caused by a CDN, hosting proxy, or web-server rule, so the right fix depends on which URLs fail and where the redirects are configured.
Identify what is looping
Before changing settings, note the exact URL that fails and when the problem began. A homepage-only loop, a site-wide loop, and a loop limited to wp-login.php or wp-admin can point to different causes. Record whether it started after a migration, HTTPS activation, plugin change, or CDN or proxy update.
- Scope: homepage, every page, or login/admin only?
- Trigger: a recent URL, SSL, plugin, CDN, or server change—or no known change?
- Address consistency: do the scheme (HTTP or HTTPS), hostname (such as www or non-www), and any installation subdirectory match across settings?
These clues narrow the search; they do not identify a cause on their own. WordPress lists conflicting URL settings and redirect rules at the CDN, proxy, host, Nginx, or Apache layer among possible sources of a loop. See WordPress’s login troubleshooting guidance.
Check the WordPress site URLs
In the dashboard, open Settings → General and compare WordPress Address (URL) with Site Address (URL). Both should use the intended scheme and hostname, and include the correct path if WordPress is installed in a subdirectory. WordPress says the values should include https:// when appropriate and should not end with a slash; consult its migration guidance before changing them.
#1 Best Overall
| Setting | What it represents | What to verify |
|---|---|---|
| Site Address | The public address visitors use to reach the site. | It matches the intended public scheme, hostname, and site path. |
| WordPress Address | The address where WordPress core application files reside. | It matches the actual location of those files, including a subdirectory if applicable. |
These values can legitimately differ. WordPress’s home_url() reference describes the front-end site URL; site_url() reference concerns the URL for WordPress application files. Do not force the two values to match without checking the installation layout.
If the dashboard is unavailable, check whether WP_HOME or WP_SITEURL is defined in wp-config.php, then compare those values with the database options home and siteurl. A constant can override the corresponding database value, so editing the database alone may not change the effective URL. Back up before editing configuration or database values, and change only a mismatch you have confirmed.
If only login or admin loops, test cookies and plugins
For a loop confined to login or admin, clear the browser’s cookies for the affected site and try again. If that does not resolve it, temporarily disable plugins to test for a conflict. WordPress’s login troubleshooting steps describe renaming the plugins folder as a way to test when dashboard access is blocked.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall- Make sure you can restore the folder name and access the site files through your host’s file manager or SFTP.
- Temporarily rename the plugins folder, then retry the affected login URL.
- If the loop stops, restore the folder name and test plugins individually to identify the conflict. Do not leave plugins disabled as a permanent fix unless that is intended.
Clearing cookies is a diagnostic step, not a guaranteed fix. A loop affecting all pages, or one that persists after these tests, calls for checking URL settings and the infrastructure layers below.
Check HTTPS and reverse-proxy handling
Find out where TLS (HTTPS encryption) ends: at the WordPress server or at a reverse proxy, CDN, or host in front of it. If the visitor connects over HTTPS but the proxy connects to the WordPress origin over HTTP, WordPress may see the origin request as HTTP and redirect it to HTTPS repeatedly unless the proxy and WordPress handle the forwarded scheme consistently.
The WordPress HTTPS handbook warns that when WordPress is behind a reverse proxy providing SSL while WordPress itself is hosted without SSL, the relevant HTTPS settings can cause an infinite redirect loop. It describes recognizing the HTTP_X_FORWARDED_PROTO header when the proxy supplies it.
Do not copy proxy-related code blindly. The proxy must be configured to provide the expected header, and WordPress must trust it only in the architecture where it is valid. Ask your hosting provider to confirm where TLS terminates and how the origin receives the request scheme if you do not control those settings.
Look for duplicate redirect rules across layers
Once WordPress URLs and scheme handling are consistent, check whether more than one layer is forcing a redirect. For example, WordPress or a plugin may enforce HTTPS while a host, CDN, reverse proxy, Nginx, or Apache applies another rule. Conflicting www/non-www or HTTP/HTTPS rules can also send a request back and forth.
- Review redirect or HTTPS settings in WordPress plugins.
- Check CDN or DNS-proxy redirect and SSL settings, if used.
- Ask the host about hosting-level redirects or reverse-proxy configuration.
- Review Nginx or Apache rules only if you manage those server configurations.
Change one confirmed rule at a time so you can identify which change resolves the loop. Before changing .htaccess, save a copy; WordPress recommends backing it up and checking custom rewrite or redirect rules when site URLs change. See the WordPress migration guidance. If the active server layer is unclear or outside your control, ask your host or a WordPress developer to inspect the redirect chain and configuration.
Verify the fix
- Retry the exact URL that originally looped, including the same hostname and HTTP/HTTPS scheme.
- Test the homepage and the affected login or admin path, if relevant.
- If you changed permalink or rewrite rules, follow WordPress’s migration guidance to update and inspect
.htaccesscustom rules. - If the loop remains, revisit the scope and recent-change clues and check the next layer rather than making unrelated URL edits.
A redirect loop cannot be diagnosed from the browser error alone. The redirect chain, actual URL values, proxy topology, and active server rules determine which layer needs correction.
Quick Recap
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.
