WordPress Admin Redirect Loop: 3 Fast Fixes for Cloudflare Users

Getting locked out of your WordPress dashboard with a “Too Many Redirects” error is frustrating. This usually happens when your browser, your server, and your SSL provider (like Cloudflare) can’t agree on whether to use HTTP or HTTPS.

If you use Cloudflare and recently changed your SSL settings, this guide will help you fix the loop and regain access to your /wp-admin/ in minutes.

Why is the Redirect Loop Happening?

The loop occurs when your configuration is “crossed.” There are two common scenarios:

1. Flexible SSL Conflict: Cloudflare connects to your server via HTTP, but your WordPress settings are forcing HTTPS. Cloudflare asks for HTTP -> WordPress says “Go to HTTPS” -> Cloudflare asks for HTTP again. Loop.
2. Full SSL Conflict: Cloudflare expects an encrypted connection (HTTPS), but your site is strictly configured for HTTP.

Solution 1: Syncing Database URLs (Recommended)

If you can’t log in to change your settings, you can force the correct URLs through your functions.php file.

1. Access your site files via FTP or File Manager.
2. Navigate to wp-content/themes/your-active-theme/functions.php.
3. Add these lines at the very top, right after the opening <?php tag:

update_option( 'siteurl', 'http://dausruddin.com' );
update_option( 'home', 'http://dausruddin.com' );

(Note: Use http if using Flexible SSL, or https if using Full/Strict SSL).

4. Refresh your login page. Once you gain access, delete these lines from your file.

Solution 2: Cleaning up wp-config.php

Sometimes, hardcoded lines in your wp-config.php file override your database settings and cause conflicts.

Look for these lines:

define( 'WP_HOME', 'http://dausruddin.com' );
define( 'WP_SITEURL', 'http://dausruddin.com' );

1. Open your wp-config.php file in your root directory.
2. Delete them. This allows WordPress to use the values defined in your database (or the ones you set in Solution 1), which is more flexible for SSL handshakes.

Solution 3: The Cloudflare “Fix” (Flexible SSL)

If you must use Flexible SSL, you need to tell WordPress that it is “behind a proxy.” Add this code to the top of your wp-config.php file:

if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO']
'https') !== false) $_SERVER['HTTPS']='on';"

This snippet tells WordPress: “Even if the request looks like HTTP to you, it started as HTTPS at Cloudflare, so don’t try to redirect it.”

Summary Checklist for Success:

• Using Cloudflare Flexible? Set WordPress URLs to http://.
• Using Cloudflare Full/Strict? Set WordPress URLs to https://.
• Still Looping? Clear your browser cache or try an Incognito window, as redirect errors are often “stuck” in the browser’s memory.