Sooner or later, every website runs into a bug or error that's difficult to troubleshoot. Often, that's because the error itself doesn't give y'all many details. The 429 Also Many Requests fault is one such example.

We know what its most common causes are, fortunately. Since there are several potential culprits, however, y'all'll often need to try more one fix earlier you can resolve it.

In this article, we're going to talk almost what causes the 429 Too Many Requests error and what it looks like. Then we'll become over v ways y'all can troubleshoot your website if you ever come across this particular result. Let's become to work!

  • What is the HTTP 429 Mistake
  • What Causes the 429 Too Many Requests Error
  • How to Fix the 429 Also Many Requests Error (5 Methods)

What is the HTTP 429 Mistake?

The HTTP 429 mistake is returned when a user has sent likewise many requests within a short period of time. The 429 status code is intended for use with rate-limiting schemes.

Check Out Our Video Guide to the 429 Too Many Requests Mistake

What Causes the HTTP 429 As well Many Requests Error

In some cases, when your server detects that a user agent is trying to access a specific folio too often in a short flow of time, it triggers a charge per unit-limiting feature. The most mutual example of this is when a user (or an attacker) repeatedly tries to log into your site.

However, your server may also place users with cookies, rather than by their login credentials. Requests may as well be counted on a per-request basis, across your server, or across several servers. And then there are a variety of situations that can result in you seeing an error similar one of these:

  • 429 Besides Many Requests
  • 429 Error
  • HTTP 429
  • Error 429 (Too Many Requests)

The error may also include additional details regarding the reason for the 429 status code, and how long the user must look before attempting to log in once again. Here's an example of what that might expect like:

          HTTP/1.one 429 Too Many Requests Content-type: text/html Retry-After: 3600        
          <html> <head> <title>Too Many Requests</title> </head> <body> <h1>Also Many Requests</h1> <p>I only allow 50 requests per hour to this website per logged in user. Try again soon. </p> </body> </html>

Regardless of how the mistake appears, it always means the same thing – there's a user or a snippet of lawmaking that'southward overwhelming your server with as well many requests. Sometimes, the problem tin become away on its ain. In other situations, such equally those acquired by problems with a plugin or Denial of Service (DDoS) attacks, you'll need to exist proactive in order to resolve the error.

The problem is that the 429 fault almost often affects your login page, which can make it impossible for you to admission your website'due south dashboard. That can make fixing it a footling catchy, but information technology's still achievable if yous know what to try.

How to Fix the 429 Too Many Requests Error (v Methods)

As you might imagine, we deal with a lot of WordPress support requests due to the nature of the services nosotros offer. That means we're intimately familiar with the 429 error, and its many potential causes.

In the post-obit sections, we'll cover five of the near common causes we've seen for the 429 Besides Many Requests error in WordPress. For each potential event, nosotros'll also teach you how to go almost fixing it, so yous can get your site support and running rapidly.

one. Alter Your WordPress Default Login URL

Creature-force login attempts are ane of the leading causes of the 429 fault on WordPress websites. One quick way to prevent attackers from trying to break through your WordPress login folio is to change its URL from the default pick, and then they can't find it in the start place.

By default, you lot tin can detect your login page by navigating to yourwebsite.com/wp-admin. That'south pretty easy to remember, but information technology's besides downright insecure since everyone on the web will know exactly where to access it.

Subscribe Now

The easiest way to change your default WordPress URL is by using the free WPS Hibernate Login plugin:

WPS Hide Login
WPS Hide Login plugin

Let'due south walk through the process of using this particular tool. You'll kickoff want to install and activate the plugin simply as you would any other, and then navigate to the Settings > WPS Hide Login tab in your WordPress dashboard:

Changing login URL
Irresolute the login URL

Here, yous can easily change your login URL by typing in any extension you lot'd like to use. Make certain to stay abroad from piece of cake-to-estimate options such as login, wp-login, and then on. This would defeat the purpose of changing your URL in the offset place, so you'll want to come up with something unique to your site.

Note that this plugin besides enables you to redirect users who try to admission your old login URL to some other page. For example, the default option will prove anyone who tries to visit /wp-admin a 404 error page, and so they'll know they're looking in the wrong place. When you lot're done, remember to save the changes to your settings, and you lot'll be good to go.

2. Disable the Really Unproblematic SSL Plugin and Replace Your Internal Links

These days, there's no good reason you shouldn't have a Secure Sockets Layer (SSL) document fix for your website. Likewise, your unabridged website should load over HTTPS. This is far more secure than using the older HTTP protocol, and information technology can fifty-fifty take a positive consequence on your site's Search Engine Optimization (SEO).

When information technology comes to enforcing HTTPS use, you can either utilise the manual route – such as an .htaccess redirect – or a plugin. I of the most popular choices is Actually Simple SSL:

Really Simple SSL
Really Simple SSL plugin

This plugin's entreatment is that it forces your unabridged website to load over HTTPS with just a couple of clicks. However, in our experience, it can also lead to occasional bugs. For example, under some circumstances, it tin can trigger the 429 mistake nosotros've been talking nigh.

There's nothing inherently wrong with this plugin, but it'south definitely non the best way to implement HTTPS use. The problem is that, even if you lot implement HTTPS manually, you're still left with the trouble of what to practice near internal links. Chances are in that location are a lot of internal links throughout your website, so you'll need to discover a way to replace all of them with their HTTPS versions after disabling the plugin.

Start, you'll desire to accept intendance of the plugin itself. If you take admission to the WordPress admin surface area, disabling Actually Unproblematic SSL shouldn't be an result – just striking Deactivate and you're done:

Deactivating really simple ssl
Deactivating the Actually Elementary SSL plugin

However since the 429 Too Many Requests Error oft blocks you from accessing your dashboard, you might have to accept the manual route and disable the plugin using an FTP client.

Either way, once the Really Elementary SSL plugin is gone, the 429 fault should be resolved. That means you tin can access your dashboard to gear up a new plugin, which will help you replace all of your internal links in i swoop. That plugin is chosen Search and Replace:

Search and Replace
Search and Supersede plugin

Get ahead and activate the plugin, so navigate to the Tools > Search & Replace tab in WordPress. Inside, select the wp_postmeta table, so enter the following parameters alongside the Search for and Supervene upon with fields respectively:

If your site uses a not-www domain:

http://yourwebsiteurl.com
https://yourwebsiteurl.com

In some cases, at that place may exist world wide web instances of your domain in the database as well, then we besides recommend running another search and supervene upon with the settings below.

http://www.yourwebsiteurl.com
https://yourwebsiteurl.com

If your site uses a www domain:

http://www.yourwebsiteurl.com
https://www.yourwebsiteurl.com

To replace non-www instances of your domain in the database, run another search and supplant with the settings below:

http://www.yourwebsiteurl.com
https://yourwebsiteurl.com

Then select the dry run option, which will let you know how many instances of your HTTP URLs the plugin will supplant within your database. After that dry run, execute the plugin for existent and it will replace all the necessary links.

Keep in mind that after disabling the Actually Unproblematic SSL plugin, yous'll also need to set up a site-wide HTTPS redirect using your .htaccess file. This volition enable yous to implement HTTPS finer, without the adventure of further 429 errors.

3. Temporarily Conciliate All of Your WordPress Plugins

So far, we've focused on a unmarried plugin that may cause the 429 fault. However, in do, whatsoever plugin could cause this result if it makes too many external requests. If neither of the above methods leads to a solution in your example, it may be time to try disabling all of your plugins at once, to ensure that they aren't the problem.

For this department, we'll presume you don't have access to your dashboard and tin't disable plugins the usual fashion. In that case, you'll need to access your website via FTP using a customer such as Filezilla, and navigate to the public_html/wp-content/ directory.

Within, there should be several folders, one of which is chosen plugins:

Plugins folder
Plugins folder

Right click on that folder, and change its proper noun to something else, such equally plugins.deactivated. One time you do that, WordPress won't exist able to 'find' any of the plugins, and information technology will automatically conciliate all of them. However, before you lot try to access your site again, get ahead and create a new empty folder called plugins, so WordPress will still function as normal.

If the 429 error is gone when y'all adjacent visit your site, you can assume that one of the plugins you turned off was the culprit. That means you lot need to narrow downward which one caused the trouble. To exercise that, yous'll desire to:

  1. Delete the empty plugins directory you ready a infinitesimal ago, and restore the previous folder to its original proper name.
  2. Access the plugins directory.
  3. Rename one of the plugin folders within to anything else, which will deactivate only that specific plugin.
  4. Attempt to admission your website, and run into if the 429 fault is gone.
  5. If the error persists, return that plugin folder to its original name and repeat steps three and 4 with the next i.

By moving downwards your list of active plugins i past one, you should somewhen discover which one is the culprit. Once you figure out which plugin is behind the 429 Too Many Requests error, you tin can delete it altogether, which should fix the outcome.

4. Switch to a Default WordPress Theme

If information technology turns out that a plugin isn't the crusade of your 429 fault, information technology's possible that your agile theme might exist at mistake. To figure out if that'southward the case, you can disable your active theme manually, forcing WordPress to switch to one of the default templates that ships with the CMS.

This process works much the aforementioned equally disabling plugins manually. You'll want to launch your trusty FTP customer over again, and this time navigate to the public_html/wp-content/themes directory. Once there, look for the folder that corresponds to your active theme and rename it to annihilation else you want.

If you lot try to access your website after that, the 429 Too Many Requests error should be gone. You'll also notice that everything looks quite a bit different. Don't panic, though, your theme and all of its customizations are nonetheless there.

All you need to do is render the theme folder to its original proper name and activate information technology again. If the 429 fault returns afterward, so y'all might need to contact the theme'southward developers or consider changing your site's theme and delete information technology eventually.

5. Contact Your Host If You Nevertheless Can't Resolve the Mistake

In some instances, it's possible that the crusade backside the 429 error originated with your server, rather than with your website itself. If this is the case for y'all, no amount of work on your part will be able to fully resolve the problem.

For example, some spider web hosts will cake requests from specific third-party services or platforms. These can include search engines, crawlers, and other apps (such as Google Search Console) that make large numbers of requests to your website.

Contacting your hosting provider and asking them to allow these requests can solve the issue. Additionally, fifty-fifty if limitations placed on your server past your host aren't the cause of the problem, they may be able to provide valuable insight and advice that can help you lot detect the correct solution.

Getting the 429 Too Many Requests mistake message? That'due south a bummer but don't despair, nosotros've got y'all covered with our guide!😭🤗 Click to Tweet

Summary

Encountering an error on your website is always frustrating. However, every bit far equally errors go, those with number codes at least give you plenty information to start fixing them. If you run into the 429 Too Many Requests error, you'll know that something is overwhelming your server with too many requests, then information technology's only a matter of identifying what the source of the problem is.

If you do happen to experience the 429 error, here are v ways you lot tin can go virtually troubleshooting it:

  1. Change your default WordPress login URL.
  2. Disable the Actually Unproblematic SSL plugin.
  3. Temporarily conciliate all of your WordPress plugins.
  4. Switch to a default WordPress theme.
  5. Contact your host if yous still can't resolve the error.

Do you have any questions most how to prepare the 429 Besides Many Requests error in WordPress? Let's talk about them in the comments section below!

Save time, costs and maximize site performance with:

  • Instant help from WordPress hosting experts, 24/7.
  • Cloudflare Enterprise integration.
  • Global audience attain with 32 data centers worldwide.
  • Optimization with our built-in Awarding Functioning Monitoring.

All of that and much more, in one plan with no long-term contracts, assisted migrations, and a 30-twenty-four hours-money-back-guarantee. Bank check out our plans or talk to sales to find the plan that's right for y'all.