How to Fix the “Too Many Redirects” Error on Your WordPress Blog

How to fix the Too Many Redirects Error in WordPress

Introduction

A WordPress website can sometimes suddenly stop loading and display an error such as “Too Many Redirects”, “This page isn’t working”, or “ERR_TOO_MANY_REDIRECTS.”

This problem can be frustrating because your website may have been working perfectly before the error appeared.

The Too Many Redirects Error usually happens when your website gets stuck in a redirect loop. Instead of loading the requested page, the browser is repeatedly sent from one URL to another.

For example, your website might redirect from HTTP to HTTPS, while another setting tries to send the HTTPS version back to HTTP. This creates an endless loop.

The good news is that this problem is usually fixable. In most cases, you don’t need to reinstall WordPress or rebuild your website.

Common causes include incorrect WordPress URL settings, SSL configuration, plugins, .htaccess rules, caching systems, themes, or CDN settings.

In this guide, you’ll learn several practical ways to identify and fix the problem.


Why Should You Change the WordPress Login URL?

WordPress websites commonly receive automated requests to the default login endpoints.

Attackers and bots may repeatedly try:

  • /wp-login.php
  • /wp-admin/
  • Common usernames
  • Previously leaked passwords
  • Password combinations generated automatically

Changing the login URL doesn’t make your website invisible, but it can reduce the amount of automated traffic hitting the standard login endpoint.

It can also reduce unnecessary login attempts that consume server resources.


What Is a Brute Force Attack?

A brute force attack is an automated attempt to gain access to an account by repeatedly trying different username and password combinations.

For example, a bot might try:

admin / password123
admin / 123456
admin / wordpress

and continue with thousands of combinations.

If an administrator uses a weak or reused password, these attacks can become particularly dangerous.

That’s why changing the login URL should be combined with other security measures.


Is Changing the Login URL Enough for WordPress Security?

No.

Changing the login URL can reduce automated attacks against the default endpoint, but it doesn’t protect your website by itself.

For stronger protection, combine it with:

  • Strong unique passwords
  • Two-factor authentication
  • Login attempt limits
  • Security plugins
  • Regular WordPress updates
  • Updated plugins and themes
  • Secure hosting
  • Regular backups

Internal Link:

https://wpwitharb.com/backup-your-wordpress-site/


Before You Change the Login URL

Before making any security changes, create a complete backup of your WordPress website.

You should have a backup of:

  • WordPress files
  • Database
  • Themes
  • Plugins
  • Media uploads

Also make sure you have access to your hosting File Manager or another recovery method.

This is especially important because an incorrectly configured login URL can temporarily lock you out of the WordPress dashboard.


Method 1: Change WordPress Login URL Using a Security Plugin

The easiest method for most beginners is to use a reputable WordPress security plugin that supports changing or hiding the login URL.

A plugin can handle the required WordPress configuration without requiring you to manually edit core files.

After installing a suitable security plugin:

  1. Open the plugin settings.
  2. Find the login security section.
  3. Locate the login URL option.
  4. Enter your new login slug.
  5. Save the settings.
  6. Open the new login URL in a private browser window.
  7. Log in to confirm everything works.

Choose a login slug that isn’t obvious.

For example:

yourdomain.com/secure-login/

Avoid predictable slugs such as:

login
admin-login
wp-login-new
wordpress-login

A less obvious URL makes automated targeting more difficult.

Common causes of the Too Many Redirects Error in WordPress


Choose a Secure Login Slug

Your new login URL doesn’t need to be complicated, but it shouldn’t be easily guessable.

For example:

yourdomain.com/member-access/

is less predictable than:

yourdomain.com/login/

Don’t use personal information such as:

  • Your name
  • Date of birth
  • Business phone number
  • Email address
  • Domain registration details

The goal is to make automated discovery harder.


Test the New Login URL

After changing the login URL, don’t immediately log out of your current session.

First open an Incognito or Private browser window.

Enter your new login address.

For example:

https://yourdomain.com/member-access/

Confirm that:

  • The login form appears.
  • Your username and password work.
  • The WordPress dashboard opens normally.
  • You can log out and log back in.
  • The old login URL no longer provides the normal login form.

Only after testing everything should you close your original administrator session.


What Happens to the Old Login URL?

After the login URL has been changed correctly, the standard login endpoint should no longer provide the normal WordPress login page in the same way.

This is important because simply creating another login page without changing the underlying login behavior doesn’t provide the security benefit you’re looking for.

Always test both the old and new URLs after making the change.


Use Two-Factor Authentication Too

Changing the login URL is only one part of a secure WordPress setup.

Two-factor authentication adds another verification step after the password.

Even if an attacker somehow obtains your password, they may still be unable to access the account without the second authentication factor.

For administrator accounts, 2FA is one of the most useful additional security measures.

External Resource:

https://wordpress.org/documentation/article/administration-over-ssl/


Limit Login Attempts

Another useful security layer is limiting repeated login attempts.

For example, you can configure your security system to temporarily block an IP address after multiple failed attempts.

This helps prevent bots from continuously trying passwords.

Combine login limits with:

  • Strong passwords
  • 2FA
  • Updated plugins
  • Updated WordPress
  • A non-default login URL

This creates a much stronger security setup.


Keep WordPress Updated

Outdated WordPress installations, plugins, and themes can contain security vulnerabilities.

After you Change WordPress Login URL, continue maintaining the rest of your website.

Check regularly for updates to:

  • WordPress core
  • Plugins
  • Themes
  • PHP
  • Security software

Internal Link:

https://wpwitharb.com/deactivate-wordpress-plugins/

Use a Security Plugin Carefully

If you’re using a security plugin to Change WordPress Login URL, make sure the plugin is actively maintained and compatible with your current WordPress version.

After changing the login URL:

  1. Save the new login slug.
  2. Open a private/incognito browser window.
  3. Visit the new login address.
  4. Log in successfully.
  5. Log out.
  6. Log in again.
  7. Test the old /wp-login.php address.

Don’t delete or modify WordPress core login files just to hide the login page.


Create a Login URL That Is Difficult to Guess

Your new login slug should be unique but still easy for you to remember.

For example:

yourdomain.com/site-access/

or:

yourdomain.com/dashboard-entry/

Avoid obvious URLs such as:

yourdomain.com/login/
yourdomain.com/admin/
yourdomain.com/wp-login/

The purpose isn’t to create a complicated password-like URL. The purpose is simply to move the login endpoint away from the predictable default location.


What If You Forget the New Login URL?

This is one of the most important things to consider before you Change WordPress Login URL.

Keep your new login address stored somewhere secure, such as your password manager.

If you forget it, you can usually regain access by disabling the plugin that changed the login URL.

Using your hosting File Manager or FTP:

  1. Open:
/wp-content/plugins/
  1. Find the relevant security/login plugin folder.
  2. Rename the folder temporarily.
  3. Try accessing the standard WordPress login URL again.
  4. Log in to WordPress.
  5. Restore the plugin folder name.
  6. Review its settings.

The exact recovery process depends on the plugin you’re using.

Internal Link:

https://wpwitharb.com/deactivate-wordpress-plugins/


Don’t Edit WordPress Core Files

Never modify or rename:

wp-login.php

directly to hide your login page.

WordPress core files are replaced during updates, and manually changing them can create maintenance and security problems.

A properly maintained security plugin is generally a better approach for beginners.


Add Two-Factor Authentication

Changing the login URL reduces exposure to automated login requests, but two-factor authentication (2FA) provides another layer of protection.

With 2FA enabled, logging in requires an additional verification step after entering the password.

For administrator accounts, consider using:

  • Authenticator apps
  • Security keys
  • Backup authentication codes

If someone obtains your password, 2FA can help prevent unauthorized access.


Use Strong Administrator Passwords

A hidden login URL doesn’t compensate for a weak password.

Your administrator password should be:

  • Long
  • Unique
  • Difficult to guess
  • Different from passwords used elsewhere

Avoid passwords containing:

admin
wordpress
123456
yourdomain
yourname

A password manager can generate and store strong passwords for your administrator account.


Limit Failed Login Attempts

Another useful protection is limiting repeated login attempts.

If an attacker repeatedly sends incorrect passwords, your security system can temporarily block or slow down those requests.

Combine this with:

  • A custom login URL
  • Strong passwords
  • 2FA
  • Security monitoring
  • Regular backups

This creates a much stronger WordPress security setup.


Clear Your Website Cache

After you Change WordPress Login URL, clear all relevant caches.

Check:

  • WordPress caching plugin
  • Hosting cache
  • CDN cache
  • Browser cache

This is particularly important if your website uses aggressive page caching.

Open the new login page in a private browser window after clearing the cache.


Check Your Security Plugin Settings

After changing the login URL, review your security plugin’s settings.

Make sure you haven’t accidentally enabled a setting that:

  • Blocks administrators
  • Disables XML-RPC unexpectedly
  • Blocks your own IP address
  • Prevents legitimate users from logging in
  • Conflicts with another security plugin

Running multiple security plugins with overlapping login protection can sometimes create conflicts.


Step by step guide to fix Too Many Redirects Error in WordPress


Monitor Login Attempts

After you Change WordPress Login URL, monitor your site’s security logs.

Look for:

  • Failed login attempts
  • Repeated requests
  • Unknown administrator logins
  • Suspicious IP addresses
  • Unexpected password-reset requests

If you notice unusual activity, change compromised credentials immediately and investigate the account.


Create Regular WordPress Backups

Security changes should always be accompanied by a reliable backup strategy.

Create regular backups of:

  • Database
  • WordPress files
  • Themes
  • Plugins
  • Media uploads

Keep at least one backup separate from your live website.

Internal Link:

https://wpwitharb.com/backup-your-wordpress-site/

A recent backup gives you a recovery option if a security plugin, update, or configuration change causes a problem.


Common Mistakes to Avoid

Using an Obvious Login Slug

Changing /wp-login.php to /login/ doesn’t provide much benefit because /login/ is easy to guess.

Forgetting the New URL

Always save the new login address securely before logging out.

Editing WordPress Core

Don’t rename or modify wp-login.php.

Using Multiple Security Plugins

Two plugins trying to control login behavior can cause unexpected conflicts.

Skipping Backups

Always create a backup before making major security changes.

Relying Only on a Hidden Login URL

A custom login URL is only one security layer. Use strong passwords and 2FA as well.


Frequently Asked Questions

Does changing the WordPress login URL stop brute force attacks?

It can reduce automated attacks against the standard WordPress login endpoint, but it does not completely stop brute force attacks. Strong passwords, 2FA, login limits, and other security measures are still important.

Is it safe to change the WordPress login URL?

Yes, when it’s done through a reputable and properly maintained security plugin. Always test the new URL before ending your existing administrator session.

Will changing the login URL affect my WordPress SEO?

Changing the administrator login URL normally doesn’t affect your public posts or pages because the login endpoint isn’t your normal search-engine content.

What happens if I forget my custom login URL?

You can generally recover access by temporarily disabling the plugin responsible for changing the login URL through File Manager or FTP, then restoring the plugin after logging in.

Should I use 2FA after changing the login URL?

Yes. A custom login URL and 2FA protect different parts of the login process, so using both provides stronger protection than relying on either one alone.


Related Articles

For more WordPress security and troubleshooting guides:


Helpful External Resources


Final Thoughts

Learning how to Change WordPress Login URL is a useful step toward reducing automated attacks against the standard WordPress login endpoint. However, it shouldn’t be considered a complete security solution.

For the best protection, combine your custom login URL with a strong unique administrator password, two-factor authentication, login-attempt protection, regular updates, and reliable backups.

Most importantly, test your new login address before logging out of your existing administrator session and keep the new URL stored somewhere secure. This simple precaution can prevent you from accidentally locking yourself out of your own website.

 

Leave a Comment

Your email address will not be published. Required fields are marked *