Fix 429 Too Many Requests Error
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 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 the 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!
What is the HTTP 429 Error
What Causes the 429 Error of Too Many Requests?
How to Resolve the Error 429: Too Many Requests (5 Methods)
How to Fix WordPress’s 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 the HTTP 429 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.
The HTTP 429 Too Many Requests Error is caused by a number of factors.
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.
Cookies, rather than login credentials, may be used by your server 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:
There are 429 requests that are excessive.
Error 429 in HTTP (Too Many Requests)
Additional information about the reason for the 429 status code, 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:
429 HTTP/1.1 There Are Too Many Requests
Type of content: text/html
html> html> html> html> html> html> html> html> html> html> html> html> html> html
</title> \s</head> \s<body> \s<h1>
There Are Too Many Requests
Per logged in user, I only allow 50 queries per hour to this website. Please try again soon. </p>
Regardless of how the error appears, it always signifies the same thing: a user or a piece of code is sending too many requests to your server. It’s possible that the issue will go away on its own. You’ll 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 issue is that the 429 error frequently impacts your login page, making it impossible for you to access the dashboard of your website. Fixing it can be difficult because of this, but it is still possible if you know what to try.
How to Fix the 429 Too Many Requests Error (5 Methods)
Because of the nature of the services we provide, we receive a lot of WordPress help queries. As a result, we’re well familiar with the 429 error and its various causes.
We’ll go over five of the most prevalent causes for the 429 Too Many Requests 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.
1. Modify the URL of your WordPress login page.
One of the most common causes of the 429 error 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 your website.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:
WPS Login Hide
WPS Hide Login is a plugin that allows you to hide your login information.
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:
Do you want to discover how we grew our traffic by over 1000%?
Join the 20,000+ people who receive our weekly email with WordPress insider secrets!
Now is the time to subscribe.
Modifying the login URL
The login URL can be changed.
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 a 404 error page to anyone trying to access /wp-admin, 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.
2. 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:
SSL in a Nutshell
SSL plugin that is extremely easy to use
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 integrating 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:
Deactivating a very basic SSL certificate
The Really Simple SSL plugin is deactivated.
However, because the 429 Too Many Requests Error frequently prevents you from accessing your dashboard, you may need to disable the plugin manually using an FTP client.
In any case, the 429 error should be addressed after the Really Simple SSL plugin is removed. That means you may use your dashboard to install a new plugin that will automatically replace all of your internal links. Search and Replace is the name of the plugin.
Replace and Search
Plugin for Search and Replace
After you’ve installed the plugin, go to the Tools > Search & Replace tab in WordPress. Select the wp post meta table within and, besides the Search for and Replace with fields, insert the following parameters:
If you’re using a non-www domain, you’ll need to complete the following:
In rare cases, the database may also contain www instances of your domain, thus we recommend doing another search and replacing with the parameters below.
If your website is hosted on a www domain, make the following changes:
Run another search and replace non-www occurrences of your domain in the database with the following settings:
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.
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 than 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.
To get the most out of WordPress, read our in-depth guides.
We’ll assume 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:
Plugins folder Plugins folder Plugins folder Plugins folder Plugins folder 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 429 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:
Delete the empty plugins directory that you created a minute ago, and rename the preceding folder.
Go to the plugins folder.
Change the name of one of the plugin directories within to something different to deactivate only that plugin.
Check your website to see whether the 429 problem has vanished.
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 429 Too Many Requests error, you may uninstall it and the problem should go away.
4. Change to a WordPress Default Theme
If it turns out that your 429 problem isn’t caused by a plugin, it’s possible that your active theme is to blame. You can test this by manually disabling your active theme and forcing WordPress to use one of the CMS’s default templates.
This procedure is similar to manually disabling plugins. You’ll need to restart your FTP client and travel to the public html/wp-content/themes directory this time. Look for the folder that corresponds to your current theme and rename it to whatever you like.
The 429 Too Many Requests issue should be gone if you try to access your website after that. You’ll also note that everything has changed dramatically. But don’t worry, your theme and all of your adjustments are still intact.
All you have to do now is rename the theme folder back to its original name and reactivate it. If the 429 problem persists, you should either contact the theme’s developers or consider changing your site’s theme and eventually deleting it.
5. Make contact with your host If the Error Remains Unresolved,
It’s possible that the 429 error was caused by your server rather than your website in some cases. If this is the case, no amount of effort on your behalf will be enough to solve the situation completely.
Some web hosts, for example, will refuse requests from certain third-party services or platforms. Search engines, crawlers, and other apps (like Google Search Console) that make a huge number of requests to your website are examples of these.
The problem can be resolved by contacting your hosting provider and asking them to accept certain requests. Furthermore, even if your host’s restrictions on your server aren’t the source of the problem, they may be able to offer significant information and advice that may aid you in finding the right solution.
Are you getting the 429 Too Many Requests error? That’s unfortunate, but don’t worry; our guide has you covered!
TO TWEET, CLICK HERE
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 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.
If you run into the 429 problem, there are five things you can do to fix it:
Make a change to your WordPress login URL.
Remove the Really Simple SSL plugin from your system.
Deactivate all of your WordPress plugins for the time being.
Change to a standard WordPress theme.
If you’re still having trouble, contact your host.
Do you have any queries regarding how to resolve the WordPress 429 Too Many Requests error? Let’s have a conversation about them in the comments box below!
Save time, money, and improve site performance by using:
Expert WordPress hosting assistance is available 24 hours a day, 7 days a week.
Integration with Cloudflare Enterprise.
With 29 data centers across the world, we can reach a global audience.
With our built-in Application Performance Monitoring, you can improve your performance.
All of this and more is included in a single plan that includes no long-term obligations, aided migrations, and a 30-day money-back guarantee. Check out our plans or speak with a sales representative to find the ideal plan for you.