Looking for qualified leads? Connect with 1,000+ potential clients on Distinguished.io.

Code 429 Too Many Requests Error: How to Resolve

Mar 09, 2022  |  

Every website, sooner or later, encounters a difficult-to-resolve fault or error. That's usually because the mistake doesn't provide a lot of information. One example is the code 429 too many requests error.

Fortunately, we know what the most prevalent reasons are. However, because there are multiple possible causes, you'll probably need to attempt more than one solution until you find one that works.

We'll go through what causes code 429 too many requests error and what it looks like in this article. Then, if you ever run into this problem, we'll go over five techniques to debug your website. 

Let's get started!

How to Fix WordPress's Code 429 Too Many Requests:

Because the user sent too many requests in a short period of time, you're getting the 429 Too Many Requests error message (could be a plugin, a DDos, or something else). It's a server requesting that you cease sending requests.

Try one of these five solutions to solve it in WordPress:

  • Change the default login URL for WordPress.
  • Examine your HTTPS internal links to see whether they're the source of the problem.
  • Turn off all of your WordPress plugins.
  • Change to a standard WordPress theme.
  • Make contact with your web hosting company.

What is HTTP Code 429 Too Many Requests Error?

When a user sends too many requests in a short period of time, the HTTP 429 error is issued. The 429 status code is meant to be used in conjunction with rate-limiting techniques.

>>> How to Fix Syntax Error in Python?

What Causes the HTTP 429 Error of Too Many Requests?

When a user agent attempts to access a given page too many times in a short period of time, your server may activate a rate-limiting function. When a user (or an attacker) tries to log into your site repeatedly, this is the most common example.

Your server may utilize cookies instead of login credentials to identify users. Requests can be counted per request, across your entire server, or across many servers. As a result, a variety of circumstances can lead to you seeing an error like one of these:

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

Additional information about the reason for the code 429 too many requests error, as well as how long the user must wait before attempting to log in again, may be included in the error. Here's an illustration of what that could look like:

HTTP/1.1 429 Too Many Requests

Content-type: text/html

Retry-After: 3600

<html>

<head>

<title>Too Many Requests</title>

</head>

<body>

<h1>Too Many Requests</h1>

<p>I only allow 50 requests per hour to this website per logged in user. Try again soon. </p>

</body>

</html>

The error always means the same thing, regardless of how it appears: a user or a piece of code is sending too many requests to your server. It's conceivable that the problem will resolve itself. You need to be proactive in other cases, such as those caused by plugin issues or Denial of Service (DDoS) assaults, to address the error.

The problem is that the 429 error regularly affects your login page, making it impossible to access your website's dashboard. Fixing it can be difficult because of this, but it is still possible if you know what to try.

>>> Hire the Best Website Development Companies 

Code 429 Too Many Requests Error Some Resolving Method

We'll go over some of the most prevalent causes for code 429 too many requests error issue in WordPress in the sections below. We'll also show you how to address each potential problem, so you can have your site back up and running quickly.

Modify the URL of The WordPress Login Page

One of the most common causes of the 429 errors on WordPress websites is brute-force login attempts. Change the URL of your WordPress login page from the default choice to make it harder for attackers to find it in the first place.

Your login page can be found by going to yourwebsite.com/wp-admin by default. That's simple to remember, but it's also insecure because everyone on the internet will know where to get it.

Using the free WPS Hide Login plugin is the simplest approach to change your default WordPress URL:

Let's have a look at how to use this particular tool. Install and activate the plugin as you would any other, and then go to your WordPress dashboard's Settings > WPS Hide Login tab:


You may easily change your login URL here by entering in whichever extension you choose. Make sure to avoid alternatives like login, wp-login, and others that are easy to guess. You'll want to come up with something unique to your site to avoid defeating the goal of altering your URL in the first place.

Users who try to visit your previous login URL will be redirected to another page using this plugin. The default option, for example, will display to anyone trying to access /wp-admin a 404 error page, letting them know they're looking in the incorrect place. Remember to save your changes to your settings after you're finished, and you'll be ready to go.

Turn Off the Really Simple SSL Plugin and Replace All Internal Links

There's no reason you shouldn't have a Secure Sockets Layer (SSL) certificate installed on your website these days. Similarly, HTTPS should be used to load your complete website. This is significantly more secure than using the older HTTP protocol, and it can even help your site rank higher in search engines (SEO).

You can either use the manual route, such as an.htaccess redirect, or a plugin to enforce HTTPS usage. Really Simple SSL is one of the most popular options:

The appeal of this plugin is that it makes your complete website load via HTTPS with just a few clicks. However, in our experience, it can occasionally result in bugs. It can, for example, cause the 429 error we've been discussing in particular cases.

This plugin has nothing inherently wrong with it, however, it isn't the greatest approach to integrate HTTPS. The difficulty is that even if you manually deploy HTTPS, you'll still have to deal with the issue of internal links. Because your website is likely to have a lot of internal links, you'll need to figure out how to replace all of them with HTTPS versions after removing the plugin.

This plugin has nothing inherently wrong with it, however, it isn't the greatest approach to integrate HTTPS. The difficulty is that even if you manually deploy HTTPS, you'll still have to deal with the issue of internal links. Because your website is likely to have a lot of internal links, you'll need to figure out how to replace all of them with HTTPS versions after removing the plugin.

First and foremost, you must look after the plugin. Disabling Really Simple SSL shouldn't be a problem if you have access to the WordPress admin area simply hit Deactivate and you're done.

After you've installed the plugin, go to the Tools > Search & Replace tab in WordPress. Select the wp postmeta table within and, besides the Search for and Replace with fields, insert the following parameters.

>>> How to Fix Syntax Error in Python: A Complete Guide 

If You're Using a non-www Domain, You'll Need to Complete the Following:

http://yourwebsiteurl.com

https://yourwebsiteurl.com

In rare cases, the database may also contain www instances of your domain, thus we recommend doing another search and replacing it with the parameters below.

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

If Your Website is Hosted on a www Domain, Make the Following Changes:

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

Run another search and replace non-www occurrences of your domain in the database with the following settings:

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

Then choose the dry run option, which will tell you how many times the plugin will replace your HTTP URLs in your database. After that dry run, run the plugin in production mode, and it will automatically replace all of the relevant links.

https://terrynmic.myshopify.com/Remember that after removing the Really Simple SSL plugin, you'll need to use your.htaccess file to set up a site-wide HTTPS redirect. This will allow you to effectively implement HTTPS without the risk of more 429 failures.

3. Deactivate All of Your WordPress Plugins for the Time Being.

So far, we've concentrated on a single plugin that could be the source of the 429 error. In practice, any plugin that makes too many external requests can cause this problem. If nothing of the previous ways works for you, it's time to try disabling all of your plugins at once to be sure they're not the source of the problem.

We'll presume you don't have access to your dashboard and can't disable plugins the usual way in this part. In such a scenario, you'll need to use Filezilla to connect to your website via FTP and navigate to the public_html/wp-content/ directory.

There should be numerous folders inside, one of which should be called plugins:


Change the name of the folder to anything different, such as plugins.deactivated, by right-clicking on it. Once you've done so, WordPress won't be able to 'locate' any of the plugins and will deactivate them all immediately. However, before attempting to visit your site again, create a new empty folder called plugins to ensure that WordPress continues to function normally.

If the code 429 too many requests error is no longer present when you return to your site, you can presume that one of the plugins you disabled was the source of the problem. That means you'll have to figure out which one created the issue. To accomplish so, you'll need to complete the following:

  1. Delete the empty plugins directory that you created a minute ago, and rename the preceding folder.
  2. Go to the plugins folder.
  3. Change the name of one of the plugin directories within to something different to deactivate only that plugin.
  4. Check your website to see whether the code 429 too many requests error has vanished.
  5. If the error still occurs, rename the plugin folder and repeat steps 3 and 4 with the next one.

You should be able to figure out which one is the offender by going through your list of active plugins one by one. Once you've figured out which plugin is causing the code 429 too many requests error, you may uninstall it and the problem should go away.

>>> PHP Segmentation Fault Debug: What is it & How to solve it

Conclusion

It's always aggravating to run into a mistake on your website. When it comes to errors, though, those with number codes at least provide you with enough information to begin correcting them. When you get the code 429 too many requests error, you know something is overloading your server with too many requests, therefore it's only a matter of figuring out what's causing the issue.

Distinguished.io is the best b2b rating and review platform. Connect with the best website development companies and ensure your website operates with perfection and without errors


Leave a comment

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


You might also like

Create a Company Profile

Get your company in front of 150,000+ people in 20 minutes or less.