How to Fix WordPress Admin Too Many Redirects: Causes, Checks, and Proven Fixes

What the WordPress Admin Too Many Redirects Error Means

If you are trying to log in to wp-admin and keep getting bounced between pages, the problem is usually a redirect loop.

This article explains how to fix WordPress admin too many redirects by tracing the most common causes and applying safe, order-based fixes.

Redirect loops can be caused by bad URL settings, cookie conflicts, HTTPS mismatches, caching rules, or plugin and server-level configuration issues.

The good news is that most cases can be resolved without losing content or reinstalling WordPress.

Why This Error Happens

WordPress sends users to different URLs based on settings stored in the database, configuration files, and the web server.

When one layer says one thing and another layer says something different, the browser can get stuck in a loop.

Common triggers include:

• Incorrect WordPress Address (URL) and Site Address (URL) values
• HTTP and HTTPS conflicts after an SSL migration
• Bad browser cookies or cached redirects
• Security, cache, or login plugins rewriting authentication paths
• Misconfigured .htaccess rules or Nginx rewrite rules
• Reverse proxy or CDN settings, such as Cloudflare SSL mode mismatches

Start With the Fastest Checks

Before changing server files, rule out the simplest causes.

These quick checks often solve the issue immediately.

Clear cookies and browser cache

Redirect loops sometimes happen because the browser keeps sending outdated authentication cookies.

Open the site in an incognito window or clear cookies for the domain, then try logging in again.

Test a different browser or device

If WordPress admin works elsewhere, the issue may be local to one browser profile.

That points to cache, extensions, or saved cookies rather than a site-wide configuration error.

Verify WordPress URL Settings

One of the most common causes of the WordPress admin too many redirects error is a mismatch between the site URL and the home URL.

These values must match the real address you want users to access, including the correct protocol.

Check the values in Settings > General if you can access the dashboard.

Make sure these are consistent:

• WordPress Address (URL)
• Site Address (URL)

If you cannot access wp-admin, define them in wp-config.php with:

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

Use the exact domain and protocol your site should load with.

If your site uses www, include it consistently.

If it uses non-www, keep both values aligned to that version.

Check HTTPS and SSL Configuration

HTTPS mismatches are a major source of redirect loops, especially after installing an SSL certificate or moving to a new host.

If WordPress thinks the site is on HTTP while the browser is being forced to HTTPS, login pages may keep redirecting back and forth.

Review these common scenarios:

• The site URL is set to http:// but the server redirects to https://
• Cloudflare is set to Flexible SSL while the origin server expects HTTPS
• A security plugin forces SSL while WordPress core settings remain on HTTP
• The certificate is valid, but the server does not pass the correct HTTPS indicators to WordPress

If you use Cloudflare, Full or Full (Strict) is usually safer than Flexible when your origin server has a valid certificate.

Also confirm that WordPress URLs, the server redirect rules, and any CDN settings all point to the same protocol.

Disable Plugins That Affect Login or Redirects

Plugins are a frequent cause of login loops, especially security, cache, and redirection tools.

A plugin can override authentication paths, force a canonical URL, or store stale redirect rules.

If you can access the file system, rename the wp-content/plugins folder temporarily to disable all plugins.

Then test wp-admin again.

If the login works, restore the folder name and reactivate plugins one by one until the loop returns.

Pay special attention to plugins in these categories:

• Security plugins such as Wordfence, iThemes Security, or Sucuri
• Cache plugins such as WP Rocket, W3 Total Cache, or LiteSpeed Cache
• Redirection plugins that manage 301 and 302 rules
• Login customization plugins that change the default wp-login.php flow

Review the .htaccess File

On Apache servers, a broken .htaccess file can trigger repeated redirects.

This often happens after migration, permalink changes, or custom rewrite rules from plugins or security tools.

To test this safely, back up the current file and replace it with WordPress default rules:

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

Then try logging in again.

If the problem disappears, a custom rewrite rule or plugin-generated rule was likely responsible.

What If You Use Nginx?

Nginx does not use .htaccess, so redirect loops are usually caused by server blocks, SSL directives, or proxy rules.

Check that:

• The canonical domain is defined only once
• HTTP to HTTPS redirects are not duplicated in multiple server blocks
• Proxy headers correctly pass scheme and host information
• No rewrite rule sends wp-admin back to the public homepage

If you are behind a load balancer or reverse proxy, make sure WordPress receives the correct HTTP_X_FORWARDED_PROTO or equivalent header.

Otherwise WordPress may think the request is HTTP even when the browser is on HTTPS.

Fix Login Cookie and Authentication Issues

WordPress admin access depends on cookies being set for the right domain and path.

If the cookie domain is wrong, the login session may never stick.

Check for these problems:

• COOKIE_DOMAIN is set incorrectly in wp-config.php
• The site changed from www to non-www or vice versa
• The browser blocks third-party or cross-site cookies
• A caching layer serves a cached login page instead of the real form

If you previously added cookie constants during troubleshooting, remove them unless you are certain they are needed.

In many cases, WordPress works best without manually forcing cookie settings.

Clear Server, CDN, and Plugin Cache

Cached redirects can persist even after you correct the underlying issue.

Purge all layers you control, including the host cache, CDN cache, and plugin cache.

Use this order:

1. Clear WordPress cache plugin data
2. Flush host-level cache from your hosting control panel
3. Purge CDN cache, including Cloudflare if used
4. Clear your browser cache and cookies again

If your host offers a staging environment, test the fix there first.

That reduces the risk of affecting live traffic while you troubleshoot.

Use Recovery Mode or File Access If You Are Locked Out

If a fatal plugin issue is preventing login, WordPress Recovery Mode may still help if you have access to the email address connected to the admin account.

Otherwise, file access through FTP, SFTP, or your host’s file manager is the fastest route.

With file access, you can:

• Rename the plugin folder to disable plugins
• Edit wp-config.php to correct URLs
• Replace a damaged .htaccess file
• Inspect theme functions for custom redirect code

When the Theme or Custom Code Is the Problem

Some themes and custom snippets add redirect logic through functions.php, hooks, or must-use plugins.

If the admin loop began after a theme change or code deployment, inspect those changes first.

Look for:

• wp_redirect() calls
• Forced login redirects
• Conditional redirects based on role or device
• Custom canonical URL enforcement

Disable the theme temporarily by switching to a default theme, or rename a custom must-use plugin folder if one exists.

This can quickly reveal whether custom code is interfering with wp-admin.

Prevent the Error From Returning

Once you have fixed the issue, reduce the chance of another redirect loop by keeping URL, SSL, and caching settings consistent.

Before changing hosting, domains, or security plugins, document the current configuration and test redirects after each change.

• Use one canonical domain version only
• Keep WordPress URLs and server redirects aligned
• Avoid stacking multiple SSL enforcement rules
• Update cache and security plugins carefully
• Test login after migrations, restores, or CDN changes

Knowing how to fix WordPress admin too many redirects also means knowing where the loop starts: browser, plugin, configuration, or server.

When you troubleshoot in that order, the cause usually becomes clear quickly.