How To Fix 429 Too Many Requests Error (6 Pro Tips)

Error 429 is a kind of error that no one would like to see on their website. It can be caused by a lot of things, and in this article, we gonna take a look at ways that can help us resolve this issue.

429 Too many requests error belongs to 4xx error family and it is a very common error, many people report it. As a blogger, you have to be prepared for errors like these because they are a part of your journey, but that doesn’t mean that should get them on a regular basis.

These errors can be voided if you do certain things right, like not installing plugins from unknown sources, having a good secure host, and using a clean light theme.

Let’s learn more about Error 429.

What Exactly is 429 Too many Requests Error?

According to Mozilla.org, The HTTP 429 Too Many Requests response is a type of status code that means the user has sent too many requests in a certain amount of time (“rate limiting”). A Retry-After header might be included in this response revealing how long to wait before making a new request.

Let’s understand it in a simpler way.

There is a feature called “rate-limiting”, which stops the users from accessing a specific page repeatedly in a short period of time. So, when we see a 429 error on our site, it tells us that a user has sent way too many requests in a short period of time and your server is unable to handle it.

Some of you might be thinking that having a good host can save our site from falling into an error like this, but that’s not always true, a strong host can help us in preventing errors to some extent, but it can’t shield your site forever.

429 Error can happen with anyone doesn’t matter which host you’re using.

What Causes Error 429 Too Many Requests?

As I said earlier, this error can be caused by a lot of things, but the most common ones are below:

  • Poorly Coded Plugin
  • An Attacker
  • Bot Attack/Traffic
  • Poor Host
Poorly Coded Plugin-

Always install plugins from a genuine source and do not install plugins that are untested with your current version of WordPress.

These plugins can affect your server by sending too many requests, also, old and poorly coded plugins always invite attackers, they increase the chances of your site getting hacked.

An Attacker (Hacker)-

There is maybe an attacker trying to overwhelm your site’s server with too many requests. Make sure to set a strong password, enable two-step authentication, and update plugins and themes. Also, if you’re using Cloudflare, then enable Under Attack Mode.

Bot Attack/Traffic-

There are some companies who try to expand their market by sending bot traffic to your site. If you saw a sudden spike in traffic with an unknown source (i.e. bottraffic.com), and after that, your site got the error 429 then it indicates that your site’s server was submerged by those bots, and you need to do something about it.

Go to Cloudflare and enable Bot Fight Mode.

Poor Host-

A good powerful host can fight with attacks like these. They use powerful servers which is always ready to tackle these obstacles. Stop using cheap hosts, they do more harm to your business than good. Try Kinsta or A2 Hosting.

Other names of 429 Error

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

Hints Given By 429 Error

Most errors don’t provide any details, but this error it’s not the case. They give you a hint about how much time you would have to wait before you make another attempt to log in.

Here is an example for you:

 HTTP/1.1 429 Too Many Requests
   Content-Type: text/html
   Retry-After: 3600

In the above example, you can clearly see how much time the user has to wait. The user has to wait 3600 seconds or 1 hour.

Here is another example:

<html>
      <head>
         <title>Too Many Requests</title>
      </head>
      <body>
         <h1>Too Many Requests</h1>
         <p>I only allow 50 requests per hour to this Web site per
            logged in user.  Try again soon.</p>
      </body>
   </html>

In this example, you can see that only 50 requests are allowed per hour, which means, the user has exceeded the limit, the user now has to wait at least an hour before retry.

How To Fix 429 Too Many Requests

Follow the instructions given below to fix the 429 Too Many Requests Error. However, make sure you’ve created a backup of your website because if anything goes wrong while performing the steps, you may end up losing everything, and that would be terrible.

There are many ways to create a backup, search “how to back up a WordPress site” on Google and you would find hundreds of articles.

The below steps are arranged in the order of easy to hard.

Solution 1: Clear Browser Cache

Almost every blogger is using cache nowadays on their site to improve website performance. Caching helps to load the site faster.

Browsers stores cache version of sites to deliver a faster experience to the users, however, sometimes it backfires. If a browser stores too many cache versions, it can make it unstable and trigger the 429 error.

So, if you’re facing this issue on your site right now, then clear the browser asap. See whether it fixes the issue or not.

Also, before proceeding, I want you to export all your passwords because this would remove all information from your browsers like passwords, cache versions of sites, and cookies.

To export all your passwords, you’ll need to go to the setting of Google chrome, then under Autofill, click on Passwords, after that click on 3 vertical dots, and click Export.

How to clear cache in Google Chrome

(Don’t wanna follow the same old boring steps? Try this shortcut -hit Ctrl + Shift + Delete simultaneously on the keyboard to open the appropriate window)

  • Step 1: Open Google Chrome and Click Three Verticle Dots Visible at the Top Right Corner
  • Step 2: Click on Settings
  • Step 3: Under Privacy and Security Click Clear Browsing Data
Privacy-and-security
  • Step 4: Clear Data

Time Range should be All Time and select both Cached images and files and the Cookies and other site data options.

Click on Clear data once you’ve set up everything.

Now, wait for a minute, google chrome will clear the cache and cookies. Once it’s done with it, go to your site and refresh it, see if this resolves the issue or not.

If the issue was from the browser side, the above steps will solve the problem.

How to Clear Cache In Safari

There is a shortcut that not many people know about, Just press Command + Option E and your cache will clear automatically.

However, if you don’t like shortcuts or just wanna know the old method, then here it is:

  • Click on the Safari drop-down menu and then click Preferences.
  • Click the Advanced tab. Click the Show Develop menu in the menu bar checkbox and close the Preferences window.
  • Click the Develop drop-down menu. Click Empty Cache.

Solution 2: Enable Bot Fight Mode in Cloudflare

Bot Figh Mode is another great feature present in Cloudflare, both free and paid users can use it to secure their site from bot attacks.

You will be shocked to know that half of the internet’s traffic is now powered by bots. These bots try to scam bloggers and many websites are struggling because of them. Some website even spends thousands of dollars just to stop bots from entering their site.

But you won’t have to spend even a single dollar. Just follow the steps below to enable the Bot Fight Mode in Cloudflare.

Step 1: Login to your Cloudflare Account

If you don’t know your password, click on Forgot Password, and Cloudflare will send steps to reset your password.

Step 2: Select the Domain

If you’ve multiple domains linked with one Cloudflare account, then select the domain that is having issues.

Step 3: Click on Firewall and Select Bots

The Firewall option is visible in the left side menu. When you’ll click on it, a new sub-menu will open where you need to click on

Step 4: Turn On Bot Fight Mode
Bot Fight Mode Cloudflare

Now, wait for a minute or two, and see if this fixes the issue or not. Also, you can purchase the premium version of Cloudflare where you’ll get the “Super Bot Fight Mode” feature which is an upgraded version of Bot Fight Mode.

Solution 3: Deactivate All Your Plugins

If this error came just after installing a new plugin or updating a new plugin, then this solution can help you. Due to 429 Error you might not be able to login to your WordPress dashboard, so to deactivate all the plugins, we’ll go to our cPanel (Hosting Panel).

The steps shown below involves risk, do not try them if you don’t have any backup copies of your website.

Step 1: Login to your cPanel

Type yourdomain.com/cpanel to reach the cPanel login page, it’s a shortcut. If you don’t remember your ID and Password, then check the email you received just after purchasing your hosting plan.

Step 2: Click on File Manager

The File Manager option is visible under Files. Click on it to open it.

Step 3: Open Public_html Folder

The Public_html folder is one of the most important things in the cPanel because it contains the most important files and information of your WordPress. Double click on it open it.

Step 4: Open Wp-Content Folder

Under Public_html, there is another folder called Wp-content. This folder contains information about plugins and themes. Double-tap on it to open it.

Step 5: Rename Plugins Folder

Under the Wp-Content folder, you’ll find the Plugins folder.

Select Plugins folder, then right-click on it to find the Rename option, or simply click on the “Rename” option visible at the top menu.

You have to rename the Plugins folder to something else like Plugins2 or PluginTest. Once you’ve changed the name, click on “Rename” to save it.

As you can see in the above screenshot, I’ve named the plugins folder as “plugins2”.

Step 6: Check Your Website

Go to your website and refresh it, if it is working, then it indicates that a plugin was causing the issue.

Step 7: Rename Plugins Folder Back to its Original Name

Go to cPanel again and open the Wp-Content folder. Change the name of the plugins folder to its original name (plugins).

For example, I had renamed the plugins folder as “Plugins2”, so I’ll change the name back to “plugins”.

Click on “Rename File” after changing the name back to the original name (plugins).

Solution 4: Deactivate Really Simple SSL

Really Simple SSL is a great plugin, there is doubt about it, however, this plugin can trigger 429 Too Many Requests Error.

When you install and activate Really Simple SSL on your site, it forces your entire website to load over HTTPS. Which can cause bugs and issues like 429 Error.

In my opinion, you should use your host’s SSL service because they are secure. I’m not criticizing Really Simple SSL, but using SSL from a trusted source (like your host) gives you an extra layer of security.

Also, if you don’t have extra money to spend on SSL, then connect your site with Cloudflare, it’s a free DNS service that can provide your site an SSL at no cost.

There are numerous videos available about how to connect your website with Cloudflare.

Now, due to 429 Error, you may not be able to login to your WordPress dashboard, so how to deactivate Really Simple SSL?

There are two more ways available, you can go to the plugins folder in your cPanel or use phpMyAdmin. In my opinion, using cPanel is a better option. If you still wanna know how to deactivate a plugin using phpMyAdmin, check this article by Kinsta.

How to Disable Really SImple SSL via cPanel

If you know that you are only required to disable a single plugin to resolve the issue, you can perform a similar process shown in solution number 3, but there is one change. Instead of renaming the entire plugins folder, do this instead:

  • Login to your cPanel
  • Open File manager
  • Open the Public_html Folder
  • Open Wp-Content Folder
  • Open Plugins Folder
  • Select the plugin you wanna rename (Select Really Simple SSL)
  • Rename the plugin to something else, like “Really Simple SSL test”
  • Go to your website and refresh it.
  • Come back to cPanel and change the name back to its original name (from Really Simple SSL Test to Really Simple SSL)

Now, you’ll find that the plugin has been deactivated, now you delete the plugin and connect your site with Cloudflare for SSL.

Solution 5: Check Your Server Status

If you’re using a premium hosting service, then there will be an option to check the condition of your server. The host will show you a graph that will tell you how many requests your server is getting.

If you notice a massive spike in the graph that means a bot attack has recently taken place.

In the above screenshot, you can see that the server condition of one of my sites is perfect. CPU usage is only 3%, if that crosses the 100% mark, in that scenario my website won’t work. It may show me an error like 429.

Now, if you witness a CPU usage of more than 100%, then go to Cloudflare and enable under attack mode. This would stop bots from accessing your website. Hence, the usage percentage will drop back to normal and your website will begin working.

The Under Attack Mode option is available under Quick Actions.

Solution 6: Revert Back To Default WordPress Theme

The above solutions are for people who got 429 Error on their site after installing or updating a plugin. If a theme has caused this issue, then you need to revert back to the default theme of WordPress.

The steps for that are almost similar. Instead of renaming the plugins folder, you have to rename the theme folder.

Let’s see how to do that!

Step 1: Login to your cPanel

If you don’t know your login ID and password, then check the email you received just after purchasing your hosting plan.

Step 2: Open File Manager

The File Manager option is available under “Files”

Step 3: Open The Public_html Folder

Now, click on the Public_html folder and proceed to the next step.

Step 4: Click on Wp-Content Folder

Wp-Content holds information about plugins and themes. Double click on it to open it.

Step 5: Click on the Themes Folder

Under the themes folder, all the themes that are installed on your site will be available.

Step 6: Rename the Theme

Now, rename the theme to something else. For example, I’m currently using the Contentberg theme on one of my sites, so I’m gonna name the folder as “Contentberg-2”.

You can name it anything you want. Click on “Rename File” once you’ve renamed it.

Go to your site, check it. Your site should work if the issue was from the theme side.

Note: You’ll notice something strange on your site. Don’t worry because your theme and all of its customizations are still there, but you’ve to change the name of the theme folder back to its original name.

Go back to wp-content>themes>your theme, and click edit. After that, name it back to its original name. For example, I had named it as Contentberg-2, so I will rename it as “Contentberg”

Click on “Rename File” once it’s done.

If the 429 Too Many Requests error appears again, then try deleting the theme or contact the theme developer. here is the article by Kinsta on how to delete a theme.

A Suggestion For You!

I hope the issue has been resolved by now. If it is, then congrats! if it’s not then please contact your customer support, they will definitely help you. They see issues like this on a regular basis and they know how to manage it, so please chat with your host’s customer representative, share info about your issue.

HostGator – 0824 661 4102

Bluehost – 00 1 801-765-9400

Godaddy – 040 6760 7600

SiteGround – Chat Support 24/7 – Read How To Contact SiteGround Customer Support

Hostinger – Live Chat Support 24/7 – Contact Now

Kinsta – 24/7 Live Chat Support

Cloudways – +35635500106

A2Hosting – 888-546-8946

DreamHost – 24/7 Live Chat Support

Additionally, Install a plugin called “WPS Hide Login” if your site is working because this plugin can save your site from brute-force login attempts.

Brute-force login attempts are one of the leading causes of 429 Too Many Requests. That’s why it becomes a responsibility to protect your login page from these bots. WPS Hide Login can stop attackers from trying to break through your WordPress login page 

With this plugin, you can efficiently change your login URL by typing in whatever extension you would like to use. Once it’s done you changed the login page, the attacker will see a 404 Page.

I hope this post was helpful!

Check out my other works!

How To Fix 405 Method Not Allowed Error (10 Solutions)

400 Bad Request Error (Fixed) 7 Easy Ways

How To Reduce Server Response Time (TTFB) 14 Terrific Ways

How To Permanently Fix A 403 Forbidden Error (Screenshots)

How To Fix “There Has Been A Critical Error On Your Website” (Screenshots)

Sumit
Sumit

Sumit is a regular contributor to Hostinggrow.com. He has 6 years of experience in blogging, and he loves football, his favorite player is - Lionel Messi (GOAT), but he has no hate for Ronaldo.

Articles: 54

Leave a Reply

Your email address will not be published.