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

We know what its most common causes are, fortunately. Since in that location are several potential culprits, nonetheless, you'll frequently demand to try more than one fix before you tin resolve information technology.

In this commodity, nosotros're going to talk about what causes the 429 Too Many Requests error and what it looks like. And so we'll go over five ways y'all can troubleshoot your website if you ever run across this particular upshot. Permit'southward get to piece of work!

  • What is the HTTP 429 Fault
  • What Causes the 429 Too Many Requests Error
  • How to Gear up the 429 Too Many Requests Error (five Methods)

What is the HTTP 429 Fault?

The HTTP 429 mistake is returned when a user has sent too many requests within a short menstruum 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 Too Many Requests Fault

In some cases, when your server detects that a user agent is trying to access a specific page also oft in a short menstruum of fourth dimension, it triggers a rate-limiting feature. The most mutual instance of this is when a user (or an assailant) repeatedly tries to log into your site.

Yet, your server may also identify users with cookies, rather than by their login credentials. Requests may also be counted on a per-request basis, across your server, or across several servers. So there are a variety of situations that can result in you lot seeing an error like one of these:

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

The error may too include boosted details regarding the reason for the 429 status code, and how long the user must wait before attempting to log in once more. Here'southward an example of what that might look like:

          HTTP/i.1 429 Too Many Requests Content-type: text/html Retry-Afterwards: 3600        
          <html> <head> <title>Too Many Requests</championship> </caput> <trunk> <h1>Too Many Requests</h1> <p>I only let 50 requests per 60 minutes to this website per logged in user. Try again shortly. </p> </body> </html>

Regardless of how the error appears, it always ways the same thing – at that place'due south a user or a snippet of code that'due south overwhelming your server with too many requests. Sometimes, the trouble can go away on its own. In other situations, such as those caused past issues with a plugin or Denial of Service (DDoS) attacks, yous'll need to be proactive in order to resolve the error.

The problem is that the 429 fault nearly often affects your login page, which can make it impossible for you to access your website'southward dashboard. That can brand fixing information technology a little catchy, only information technology's still achievable if you know what to effort.

How to Ready the 429 Too Many Requests Error (5 Methods)

Equally you might imagine, we deal with a lot of WordPress back up requests due to the nature of the services we offer. That ways we're intimately familiar with the 429 error, and its many potential causes.

In the following sections, we'll comprehend five of the most common causes nosotros've seen for the 429 Too Many Requests error in WordPress. For each potential issue, we'll too teach you how to become about fixing it, so you tin can become your site back up and running quickly.

one. Change Your WordPress Default Login URL

Fauna-force login attempts are one of the leading causes of the 429 error on WordPress websites. One quick manner to preclude attackers from trying to break through your WordPress login page is to modify its URL from the default selection, so they can't find it in the first place.

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

Subscribe Now

The easiest manner to modify your default WordPress URL is by using the free WPS Hide Login plugin:

WPS Hide Login
WPS Hide Login plugin

Permit's walk through the process of using this particular tool. You'll start want to install and activate the plugin merely as y'all would whatever other, and then navigate to the Settings > WPS Hide Login tab in your WordPress dashboard:

Changing login URL
Irresolute the login URL

Here, yous tin easily change your login URL by typing in whatever extension you lot'd similar to use. Make sure to stay away from like shooting fish in a barrel-to-guess options such as login, wp-login, and then on. This would defeat the purpose of changing your URL in the first identify, so you'll want to come with something unique to your site.

Note that this plugin also enables you to redirect users who endeavour to admission your old login URL to another page. For example, the default option will show anyone who tries to visit /wp-admin a 404 error page, and so they'll know they're looking in the incorrect place. When y'all're done, call back to save the changes to your settings, and you'll be good to get.

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

These days, there'south no practiced reason you shouldn't accept a Secure Sockets Layer (SSL) certificate gear up for your website. Likewise, your entire website should load over HTTPS. This is far more secure than using the older HTTP protocol, and it can even have a positive upshot on your site'southward Search Engine Optimization (SEO).

When information technology comes to enforcing HTTPS use, you can either use the transmission route – such as an .htaccess redirect – or a plugin. One of the most popular choices is Really Elementary SSL:

Really Simple SSL
Really Uncomplicated SSL plugin

This plugin's appeal is that it forces your unabridged website to load over HTTPS with just a couple of clicks. Yet, in our experience, it can likewise lead to occasional bugs. For instance, under some circumstances, information technology tin trigger the 429 mistake nosotros've been talking about.

There's nothing inherently wrong with this plugin, but it's definitely not the best fashion to implement HTTPS use. The problem is that, fifty-fifty if you implement HTTPS manually, yous're still left with the trouble of what to exercise nearly internal links. Chances are there are a lot of internal links throughout your website, so yous'll need to observe a way to replace all of them with their HTTPS versions after disabling the plugin.

Starting time, you'll want to take care of the plugin itself. If you lot have access to the WordPress admin area, disabling Really Unproblematic SSL shouldn't be an issue – but hit Deactivate and you're done:

Deactivating really simple ssl
Deactivating the Really Simple SSL plugin

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

Either way, once the Really Simple SSL plugin is gone, the 429 fault should exist resolved. That means you can access your dashboard to set upwards a new plugin, which volition help you replace all of your internal links in i dive. That plugin is called Search and Supervene upon:

Search and Replace
Search and Supersede plugin

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

If your site uses a non-world wide web domain:

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

In some cases, there may be www instances of your domain in the database also, so we also recommend running another search and replace with the settings below.

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

If your site uses a www domain:

http://world wide web.yourwebsiteurl.com
https://www.yourwebsiteurl.com

To replace non-world wide web instances of your domain in the database, run some other search and supervene upon with the settings below:

http://world wide web.yourwebsiteurl.com
https://yourwebsiteurl.com

And so select the dry run selection, which volition let y'all 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.

Continue in mind that after disabling the Really Elementary SSL plugin, you'll too need to fix upwardly a site-wide HTTPS redirect using your .htaccess file. This will enable y'all to implement HTTPS effectively, without the take a chance of further 429 errors.

iii. Temporarily Deactivate All of Your WordPress Plugins

And so far, we've focused on a unmarried plugin that may cause the 429 error. Still, in practice, any plugin could cause this issue if it makes as well many external requests. If neither of the in a higher place methods leads to a solution in your instance, it may be time to try disabling all of your plugins at in one case, to ensure that they aren't the problem.

For this section, we'll assume you don't have admission to your dashboard and can't disable plugins the usual way. In that example, you'll need to access your website via FTP using a client such as Filezilla, and navigate to the public_html/wp-content/ directory.

Inside, there should exist several folders, one of which is called plugins:

Plugins folder
Plugins folder

Right click on that folder, and change its name to something else, such as plugins.deactivated. Once you lot do that, WordPress won't be able to 'notice' any of the plugins, and it will automatically deactivate all of them. However, before you attempt to admission your site once again, go alee and create a new empty folder called plugins, then WordPress volition notwithstanding function as normal.

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

  1. Delete the empty plugins directory you lot set up a minute ago, and restore the previous folder to its original name.
  2. Access the plugins directory.
  3. Rename 1 of the plugin folders within to anything else, which volition deactivate simply that specific plugin.
  4. Try to access your website, and see if the 429 error is gone.
  5. If the error persists, return that plugin folder to its original name and repeat steps 3 and four with the next one.

Past moving down your list of active plugins one by one, you lot should eventually discover which one is the culprit. Once y'all figure out which plugin is behind the 429 Too Many Requests fault, you can delete it altogether, which should set up the issue.

iv. Switch to a Default WordPress Theme

If it turns out that a plugin isn't the crusade of your 429 error, it's possible that your active theme might be at error. To figure out if that'southward the instance, yous can disable your active theme manually, forcing WordPress to switch to one of the default templates that ships with the CMS.

This procedure works much the aforementioned equally disabling plugins manually. Yous'll want to launch your trusty FTP client in one case more, 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 y'all want.

If you lot endeavor to admission your website later that, the 429 As well Many Requests fault should be gone. You'll besides detect that everything looks quite a bit dissimilar. Don't panic, though, your theme and all of its customizations are still there.

All you need to practise is render the theme folder to its original name and activate it over again. If the 429 mistake returns afterward, then you might demand to contact the theme'southward developers or consider changing your site'south theme and delete information technology somewhen.

five. Contact Your Host If You Still Can't Resolve the Error

In some instances, it's possible that the cause behind the 429 error originated with your server, rather than with your website itself. If this is the case for you lot, no amount of work on your role volition be able to fully resolve the problem.

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

Contacting your hosting provider and asking them to permit these requests tin can solve the issue. Additionally, even if limitations placed on your server by your host aren't the cause of the problem, they may be able to provide valuable insight and advice that can assist you lot find the correct solution.

Getting the 429 Too Many Requests error message? That's a bummer but don't despair, we've got yous covered with our guide!😭🤗 Click to Tweet

Summary

Encountering an error on your website is always frustrating. However, every bit far every bit errors go, those with number codes at to the lowest degree requite yous enough information to showtime 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, so information technology'south just a matter of identifying what the source of the problem is.

If you do happen to experience the 429 mistake, here are five ways you lot can become about troubleshooting information technology:

  1. Change your default WordPress login URL.
  2. Disable the Really Simple SSL plugin.
  3. Temporarily conciliate all of your WordPress plugins.
  4. Switch to a default WordPress theme.
  5. Contact your host if you however can't resolve the mistake.

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

Relieve time, costs and maximize site performance with:

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

All of that and much more, in one plan with no long-term contracts, assisted migrations, and a 30-day-money-back-guarantee. Check out our plans or talk to sales to find the plan that's right for yous.