How to Fix WordPress ERR_TOO_MANY_REDIRECTS — Complete Guide

How to Fix It — Step by Step

1. Clear your browser cache and test in a private window. Sometimes the redirect loop is cached in the browser itself. Open an incognito or private window, or clear all cookies and cached files for your domain before changing anything on the server.

   You should see: Either the site loads normally (browser cache was the culprit) or the same error in a clean window, confirming it is a server-side issue worth digging into.

2. Set your WordPress URLs directly in wp-config.php. Open wp-config.php in your site’s root directory via FTP or your host’s file manager. Add or update these two lines just above the line that reads /* That's all, stop editing! */:

   define('WP_HOME', 'https://yourdomain.com');
   define('WP_SITEURL', 'https://yourdomain.com');

   Replace the URL with your actual domain, using the correct HTTP or HTTPS prefix.

   You should see: The site loads without a redirect error, or you can reach the WordPress admin panel again.

3. Reset your .htaccess file. Via FTP, rename your current .htaccess to .htaccess_old, then create a fresh .htaccess file in the same root directory with this default WordPress content:

   # BEGIN WordPress
   <IfModule mod_rewrite.c>
   RewriteEngine On
   RewriteBase /
   RewriteRule ^index\.php$ - [L]
   RewriteCond %{REQUEST_FILENAME} !-f
   RewriteCond %{REQUEST_FILENAME} !-d
   RewriteRule . /index.php [L]
   </IfModule>
   # END WordPress

   You should see: The site or admin panel loads after saving the new file, indicating the old .htaccess had conflicting redirect rules.

4. Disable all plugins via FTP. Navigate to wp-content/plugins/ and rename the entire folder to plugins_disabled. This deactivates every plugin at once without needing access to the admin panel.

   You should see: The site loads, confirming a plugin is responsible. Rename the folder back to plugins, then reactivate plugins one at a time — testing after each — until the loop returns, identifying the problem plugin.

5. Add the HTTPS detection constant for reverse proxies. If your site is behind Cloudflare, a CDN, or a load balancer, add this line to wp-config.php so WordPress correctly identifies incoming connections as secure:

   $_SERVER['HTTPS'] = 'on';

   You should see: The redirect loop stops because WordPress no longer attempts its own HTTPS redirect on top of the one already happening at the proxy level.

6. Correct the URLs directly in the database. Log into phpMyAdmin, open your WordPress database, and find the wp_options table. Locate the rows where option_name equals siteurl and home. Click Edit on each and update the option_value to your correct full URL — making sure both use the same HTTP or HTTPS scheme.

   You should see: The site loads correctly after updating both rows and hard-refreshing the browser.