При взаимодействии с веб-ресурсами можно столкнуться с различными проблемами. Одна их таких проблем – ошибка с кодом 429 Too Many Requests. Существует две самые распространенные причины возникновения этой ошибки сервера, с которыми нам предстоит разобраться самостоятельно.
Причины появления ошибки сервера 429
Начать следует с того, что чаще всего ошибка 429 сопровождается надписью «The user has sent too many requests in a given amount of time», что означает превышение ограничений по запросам к сайту. Соответственно, именно так происходит предотвращение DDoS-атак, которые и являются основной причиной появления рассматриваемой проблемы. Помимо самого кода, вы увидите и несколько других параметров:
Общее количество запросов.
Запросы с конкретного IP-адреса в секунду.
Количество одновременных запросов.
Общее количество запросов с одного IP-адреса.
Если же сама ошибка появляется при использовании поисковых систем или сторонних онлайн-сервисов, которые запрашивают доступ к сайту, вполне возможно, что их блокировка осуществляется со стороны хостинга в связи с тем, что количество запросов превышает ограничение. Для ее решения вам потребуется обратиться напрямую в техническую поддержку с просьбой разрешить подобные запросы.
В случае, когда есть уверенность в том, что ошибка http 429 появилась именно из-за атак на ваш ресурс, советую ознакомиться с отдельным материалом, в котором вы узнаете, как обезопасить себя от DDoS эффективными инструментами и банальными мерами предосторожности.
Подробнее: Способы защиты от DDoS-атаки
Некорректная работа плагинов WordPress
Вторая распространенная причина, которая может быть связана с регулярным появлением неполадки 429, – некорректное функционирование плагинов под управлением CMS WordPress. Для решения этой проблемы потребуется выполнить несколько несложных действий.
Для начала по очереди отключайте каждый установленный скрипт через меню управления этими компонентами. Параллельно проверяйте, появляется ли ошибка. Да, на выполнение этой задачи может уйти много времени, однако это самый эффективный метод выявления плагина, который является триггером. Отметим, что сразу несколько компонентов могут вызывать проблему, поэтому постарайтесь проверить их все.
Что касается использования плагинов, то тут всегда лучше подключать только проверенные и качественные решения. Со списком таких плагинов предлагаю ознакомиться в материале по следующей ссылке.
Если после проверки неполадка все еще не исчезла, переключитесь на стандартную тему WordPress, которая называется Twenty Seventeen. Это действие поможет понять, связана ли ошибка сервера 429 со скриптами, которые входят в пользовательский шаблон оформления сайта. В том случае, когда трудность действительно была связана с темой, придется переделать ее вручную или же подыскать новый вариант для своего веб-ресурса.
Действия со стороны обычного пользователя
Обычный пользователь, который сталкивается с неполадкой 429 при попытке просмотреть конкретный сайт, не сможет ничего предпринять самостоятельно, чтобы решить ее. Однако, если есть возможность, стоит обратиться напрямую к владельцу интернет-ресурса или администраторам, сообщив им о появившейся ошибке. Так вы дадите понять, что сайт работает не так, как это нужно, и ускорите процесс решения трудностей.
Ошибка HTTP с кодом 429 – неприятная ситуация, которая может коснуться каждого владельца сайта. Из приведенного выше материала вы поняли, что существует две основные причины, которые могут ее вызывать. Теперь остается только разобраться с каждой из них и провести проверочные работы, чтобы оперативно исправить сложившуюся ситуацию.
Код ошибки 429 Too Many Requests говорит о том, что пользователь отправлял чересчур много запросов за единицу времени. Возвращаемый сервером ответ содержит пояснение, а также может включать заголовок Retry-After. Этот заголовок указывает на время, которое необходимо подождать, прежде чем повторять запрос.
О чем свидетельствует «код 429»
Причина появления ответа с кодом 429 — большое количество запросов, которые посылают пользователи, но чаще — поисковики, боты или специальные скрипты. Возврат ошибки 429 — это способ предотвращения DDoS-атак. При выдаче ошибки учитываются такие параметры, как:
- количество элементов в запросе;
- количество запросов в секунду с одного IP-адреса;
- количество одновременных запросов с одного IP-адреса (то есть запросов, посылаемых до получения ответа на предыдущий идентичный запрос);
- общее количество одинаковых запросов с IP-адреса.
Что делать пользователю, когда в браузере появляется код ошибки «429 too many requests»
Если такое сообщение появилось явно по ошибке, свяжитесь с технической поддержкой сайта. Зачастую виновником выступает некорректно работающий плагин CMS WordPress. Если вы являетесь владельцем сайта, а ваши пользователи регулярно жалуются на возникновение ошибки 429, для того, чтобы понять, так ли это, отключите все плагины на вашем сайте и проверяйте их работу по очереди.
Причины возникновения кода «429»
Причина практически всегда состоит в том, что сайт пытаются атаковать с помощью DDoS. Изредка возможно возникновение подобной ошибки из-за некорректной работы компонентов сайта.
Вас также может заинтересовать
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 you many details. The 429 Too Many Requests error is one such example.
We know what its most common causes are, fortunately. Since there are several potential culprits, however, you’ll often need to try more than one fix before you can resolve it.
In this article, we’re going to talk about what causes the 429 Too Many Requests error and what it looks like. Then we’ll go over five ways you can troubleshoot your website if you ever run into this particular issue. Let’s get to work!
- What is the HTTP 429 Error
- What Causes the 429 Too Many Requests Error
- How to Fix the 429 Too Many Requests Error (5 Methods)
How to Fix 429 Too Many Requests in WordPress:
You’re receiving the 429 Too Many Requests error message because the user has sent too many requests in a given amount of time (could be a plugin, a DDos, or something else). It’s a server telling you to please stop sending requests.
To fix it in WordPress, try one of these 5 methods:
- Change your WordPress default login URL
- Check whether your HTTPS internal links are causing the issue
- Deactivate all your WordPress plugin
- Switch to a default WordPress theme
- Contact your hosting provider
What is the HTTP 429 Error?
The HTTP 429 error is returned when a user has sent too 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 Error
What Causes the HTTP 429 Too Many Requests Error
In some cases, when your server detects that a user agent is trying to access a specific page too often in a short period of time, it triggers a rate-limiting feature. The most common example of this is when a user (or an attacker) repeatedly tries to log into your site.
However, 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 seeing an error like one of these:
- 429 Too 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 wait before attempting to log in again. Here’s an example of what that might look like:
HTTP/1.1 429 Too Many Requests
<title>Too Many Requests</title>
<h1>Too Many Requests</h1>
<p>I only allow 50 requests per hour to this website per logged in user. Try again soon. </p>
Regardless of how the error appears, it always means the same thing – there’s a user or a snippet of code that’s overwhelming your server with too many requests. Sometimes, the problem can go away on its own. In other situations, such as those caused by issues with a plugin or Denial of Service (DDoS) attacks, you’ll need to be proactive in order to resolve the error.
The problem is that the 429 error most often affects your login page, which can make it impossible for you to access your website’s dashboard. That can make fixing it a little tricky, but it’s still achievable if you know what to try.
How to Fix the 429 Too Many Requests Error (5 Methods)
As you might imagine, we deal with a lot of WordPress support requests due to the nature of the services we offer. That means we’re intimately familiar with the 429 error, and its many potential causes.
In the following sections, we’ll cover five of the most common causes we’ve seen for the 429 Too Many Requests error in WordPress. For each potential issue, we’ll also teach you how to go about fixing it, so you can get your site back up and running quickly.
1. Change Your WordPress Default Login URL
Brute-force login attempts are one of the leading causes of the 429 error on WordPress websites. One quick way to prevent attackers from trying to break through your WordPress login page is to change its URL from the default option, so they can’t find it in the first place.
By default, you can find 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 it.
The easiest way to change your default WordPress URL is by using the free WPS Hide Login plugin:
Let’s walk through the process of using this particular tool. You’ll first want to install and activate the plugin just as you would any other, and then navigate to the Settings > WPS Hide Login tab in your WordPress dashboard:
Here, you can easily change your login URL by typing in whatever extension you’d like to use. Make sure to stay away from easy-to-guess options such as login, wp-login, and so on. This would defeat the purpose of changing your URL in the first place, so you’ll want to come up with something unique to your site.
Note that this plugin also enables you to redirect users who try to access 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, so they’ll know they’re looking in the wrong place. When you’re done, remember to save the changes to your settings, and you’ll be good to go.
2. Disable the Really Simple SSL Plugin and Replace Your Internal Links
These days, there’s no good reason you shouldn’t have a Secure Sockets Layer (SSL) certificate set 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 effect on your site’s Search Engine Optimization (SEO).
When it comes to enforcing HTTPS use, you can either use the manual route – such as an .htaccess redirect – or a plugin. One of the most popular choices is Really Simple SSL:
This plugin’s appeal is that it forces your entire website to load over HTTPS with just a couple of clicks. However, in our experience, it can also lead to occasional bugs. For instance, under some circumstances, it can trigger the 429 error we’ve been talking about.
There’s nothing inherently wrong with this plugin, but it’s definitely not the best way to implement HTTPS use. The problem is that, even if you implement HTTPS manually, you’re still left with the problem of what to do about internal links. Chances are there are a lot of internal links throughout your website, so you’ll need to find a way to replace all of them with their HTTPS versions after disabling the plugin.
First, you’ll want to take care of the plugin itself. If you have access to the WordPress admin area, disabling Really Simple SSL shouldn’t be an issue – just hit Deactivate and you’re done:
However since the 429 Too Many Requests Error often 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 error should be resolved. That means you can access your dashboard to set up a new plugin, which will help you replace all of your internal links in one swoop. That plugin is called Search and Replace:
Go ahead and activate the plugin, then navigate to the Tools > Search & Replace tab in WordPress. Inside, select the wp_postmeta table, and then enter the following parameters alongside the Search for and Replace with fields respectively:
If your site uses a non-www domain:
In some cases, there may be www instances of your domain in the database as well, so we also recommend running another search and replace with the settings below.
If your site uses a www domain:
To replace non-www instances of your domain in the database, run another search and replace with the settings below:
Then select the dry run option, which will let you know how many instances of your HTTP URLs the plugin will replace within your database. After that dry run, execute the plugin for real and it will replace all the necessary links.
Keep in mind that after disabling the Really Simple SSL plugin, you’ll also need to set up a site-wide HTTPS redirect using your .htaccess file. This will enable you to implement HTTPS effectively, without the risk of further 429 errors.
3. Temporarily Deactivate All of Your WordPress Plugins
So far, we’ve focused on a single plugin that may cause the 429 error. However, in practice, any plugin could cause this issue if it makes too many external requests. If neither of the above methods leads to a solution in your case, it may be time to try disabling all of your plugins at once, to ensure that they aren’t the problem.
For this section, we’ll assume you don’t have access to your dashboard and can’t disable plugins the usual way. In that case, 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 be several folders, one of which is called plugins:
Right click on that folder, and change its name to something else, such as plugins.deactivated. Once you do that, WordPress won’t be able to ‘find’ any of the plugins, and it will automatically deactivate all of them. However, before you try to access your site again, go ahead and create a new empty folder called plugins, so WordPress will still function as normal.
If the 429 error is gone when you next visit your site, you can assume that one of the plugins you turned off was the culprit. That means you need to narrow down which one caused the problem. To do that, you’ll want to:
- Delete the empty plugins directory you set up a minute ago, and restore the previous folder to its original name.
- Access the plugins directory.
- Rename one of the plugin folders within to anything else, which will deactivate only that specific plugin.
- Try to access your website, and see if the 429 error is gone.
- If the error persists, return that plugin folder to its original name and repeat steps 3 and 4 with the next one.
By moving down your list of active plugins one by one, you should eventually discover which one is the culprit. Once you figure out which plugin is behind the 429 Too Many Requests error, you can delete it altogether, which should fix the issue.
4. Switch to a Default WordPress Theme
If it turns out that a plugin isn’t the cause of your 429 error, it’s possible that your active theme might be at fault. To figure out if that’s 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 same as disabling plugins manually. You’ll want to launch your trusty FTP client once 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 anything else you want.
If you 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 still there.
All you need to do is return the theme folder to its original name and activate it once more. If the 429 error returns afterward, then you might need to contact the theme’s developers or consider changing your site’s theme and delete it eventually.
5. 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, no amount of work on your part will be able to fully resolve the problem.
For example, some web hosts will block 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, 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 help you find the correct solution.
Getting the 429 Too Many Requests error message? That’s a bummer but don’t despair, we’ve got you covered with our guide!😭🤗Click to Tweet
Encountering an error on your website is always frustrating. However, as far as errors go, those with number codes at least give you enough 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, so it’s only a matter of identifying what the source of the problem is.
If you do happen to experience the 429 error, here are five ways you can go about troubleshooting it:
- Change your default WordPress login URL.
- Disable the Really Simple SSL plugin.
- Temporarily deactivate all of your WordPress plugins.
- Switch to a default WordPress theme.
- Contact your host if you still can’t resolve the error.
Do you have any questions about how to fix the 429 Too Many Requests error in WordPress? Let’s talk about them in the comments section below!
This comprehensive guide will explain why HTTP 429 occurs and outline steps you can take to address it quickly. It will also cover some common misconceptions about the error, such as what causes it and if there are any ways to bypass or prevent it from happening again.
HTTP 429 does not have to mean frustration for everyone involved – with the right knowledge, solutions can be found easily! Read on for our complete guide on how to tackle Too Many Requests Error once and for all.
What Is 429 Http Status Code?
The HTTP 429 status code is an error response to a client request. This status code of Hypertext Transfer Protocol (HTTP) indicates that too many requests have been sent in a given time frame. This can occur when the server has implemented rate limiting features or due to other issues with API requests. It is also known as ‘Too Many Requests’ error, and it is seen on webpages such as login page where users are attempting multiple attempts at inputting their credentials within a short period of time.
Rate-limiting by servers helps ensure optimal performance for all users by preventing overloading caused by excessive requests from one source. The origin server identifies the client by their IP address or user account.
The HTTP 429 status code usually comes with an error message informing the user about the number of requests that have been made. This counts requests made by the client and helps to determine if they have exceeded the rate limit and how long they should wait before making any more requests. Depending on the type of service being provided, this interval may range anywhere from seconds to minutes.
At times, however, legitimate users may receive the 429 status code even if they haven’t exceeded the maximum number of requests allowed per unit of time. In these cases, there could be other factors involved such as network latency or internal server errors which cause the rate limiting feature to kick in prematurely. Additionally, some services might have higher quotas than others depending on the level of access granted – so if you’re receiving this error frequently then you might need to look into upgrading your account privileges.
Cause Of 429 Http Status Code Error
There are two main causes for this type of “too many requests” error: server-side issues or client side issues. At its original name – “HTTP Too Many Requests” – it was first intended to be used with stateful cookie application frameworks; but nowadays it can also refer to any situation where one user makes excessive calls within a fixed window of time.
For example, if you have an API receiving thousands of incoming connections from different IPs each minute, then your system will likely respond with a 429 response due to being overloaded with too many requests at once.
This problem can be solved by increasing the capacity on the backend (e.g., adding more servers) or optimizing the query logic so fewer calls are made per request. In either case, understanding which layer is causing the issue is key for a successful resolution. We’ll discuss these possibilities in further detail in the following sections.
Server Side Or Client Side Issue?
The question of whether a 429 HTTP status code error is due to server side or client side issues can be difficult to answer. To comprehend the issue, it’s necessary to understand how default WordPress login URLs, any hosting provider, and plugins all interact with each other. When a WordPress website receives too many requests in a short period of time, the server detects this and responds by issuing a retry after the header indicating that rate limiting schemes should be used. If these measures are insufficient, then the problem can arise from either the client or server side.
In cases where server-side solutions such as limiting request rates prove unsuccessful, it’s possible that the fault lies on the client side. For example, if users repeatedly enter incorrect credentials when attempting to log into their WordPress sites via the default URL, this could lead to too many requests being sent at once which causes an overload for your server. In addition, faulty WordPress plugins may also cause problems leading to the “too many requests” error.
How To Fix 429 Http Status Code Error
Wait To Send Another Request
In order to fix this issue, it is possible for users to wait before sending another request. This can help them stay within the limited number of requests allowed by the server.
There are several ways to ensure a successful retry after rate limiting occurs.
- First, count the number of requests made over a short period of time and attempt to make no more than the maximum number specified by the Retry-after header.
- Second, send a new request only if there has been sufficient time since the last one was sent; otherwise, waiting is necessary as it allows enough time between each request to avoid triggering the rate limit again.
- Thirdly, set up automated systems that will monitor exactly how many requests have been made per unit of time so that you don’t exceed your allotted quota without knowing it.
- Finally, keep track of when these limits reset and plan accordingly so that they are not exceeded again shortly afterwards.
Effective monitoring and tracking techniques can go a long way towards avoiding 429 errors altogether – or at least minimizing their frequency.
Clear Your Browser’s Cache
Your browser’s cache is a temporary storage location where it saves website data such as images, scripts, and other files to help load the page faster the next time you visit it. However, sometimes the cached data can become corrupted or outdated, leading to errors like HTTP 429.
Clearing your browser’s cache can fix this issue because it removes the old or corrupted data and forces your browser to download new data from the website. This means that your browser will have a fresh start when you visit the website again, and you will no longer be sending the same request repeatedly.
To clear your browser’s cache, you can follow these simple steps:
- Open your browser and go to the settings menu.
- Look for the option to clear browsing data or history.
- Select the option to clear cached images and files.
- Choose the time range for which you want to clear the cache (e.g., last hour, last day, all time).
- Click on the clear data or delete button.
After clearing your browser’s cache, you should be able to visit the website again without encountering the HTTP 429 error. If the error persists, you can try the next possible fixes.
Flush Your DNS Cache
Another solution to the HTTP error 429 is to flush your DNS cache. DNS (Domain Name System) is responsible for converting website names into IP addresses that your browser can understand. When you visit a website, your computer stores the IP address in its DNS cache to help load the page faster in the future. However, sometimes the cached data can become outdated or corrupted, leading to errors like HTTP 429.
Flushing your DNS cache can fix this issue because it removes the old data and forces your computer to obtain new IP addresses from the website’s server. This means that your browser will have a fresh start when you visit the website again, and you will no longer be sending the same request repeatedly.
To flush your DNS cache, you can follow these steps:
- Open the command prompt on your computer. On Windows, you can do this by pressing the Windows key + R, typing “cmd” and pressing Enter. On Mac, you can open the Terminal app.
- In the command prompt, type the command “ipconfig /flushdns” (without the quotes) and press Enter.
- Wait for the command to complete. You should see a message that says “Successfully flushed the DNS Resolver Cache”.
- Close the command prompt and try visiting the website again.
After flushing your DNS cache, you should be able to visit the website again without encountering the HTTP 429 error. If the error persists, you can try the next possible fixes.
Implement Exponential Backoff
Exponential backoff is a technique that can help you avoid HTTP error 429 by slowing down the rate at which you send requests to a server. When you receive an HTTP 429 error, it means that you have exceeded the number of requests allowed by the server within a specific time period. By implementing exponential backoff, you can reduce the frequency of your requests and avoid triggering the error.
Exponential backoff works by increasing the time between each request exponentially. For example, if you receive an HTTP 429 error after sending a request, you can wait for a certain amount of time before sending the next request. If you receive another error, you can double the waiting time before sending the next request. This way, you gradually increase the time between requests until you reach a point where the server can handle your requests without returning an error.
To implement exponential backoff, you can follow these steps:
- When you receive an HTTP 429 error, wait for a certain amount of time before sending the next request. The waiting time can be determined by the server’s retry-after header or by a predefined value.
- If you receive another HTTP 429 error, double the waiting time and try again.
- Repeat step 2 until you no longer receive an HTTP 429 error.
- Once you have successfully sent a request, reset the waiting time to its initial value.
Implementing exponential backoff can help you avoid HTTP error 429 and improve the reliability of your application or website. However, it is important to balance the waiting time with the user experience. You don’t want your users to wait too long before they receive a response. Therefore, it is recommended to start with a short waiting time and gradually increase it until you find the optimal value for your application.
How To Fix Http 429 Error On WordPress
Temporarily Deactivate All Of Your WordPress Plugins
In this section we look at one of the common solutions: temporarily deactivating all WordPress plugins in your plugins directory.
This can quickly help identify which plugin is causing the issue and resolve it without any major disruption. It’s important to note that active plugins are often responsible for overloading a server and resulting in HTTP 429 error messages being sent out by the browser or app. Deactivating them will reduce these requests and thus fix the problem.
The steps to do so are straightforward:
- firstly, access your website’s dashboard;
- secondly, select ‘Plugins’ from the menu;
- thirdly, deactivate every single plugin.
This should be done as soon as possible after receiving an HTTP 429 error message, otherwise there could be more serious problems caused by excessive server overloads. Once you have managed to fix the error by disabling all your plugins, you’ll need to troubleshoot each individual plugin until you find the source of the issue before reactivating them again.
Overall, resolving HTTP 429 errors by temporarily disabling WordPress plugins is a relatively simple solution that can provide rapid results. With careful monitoring and configuration adjustments, however, further issues can typically be avoided in the future – making sure users don’t experience unnecessary disruptions while accessing your site content.
Here are some other things to consider when dealing with 429 errors:
- Check whether your host has set hard limits on resources such as CPU time or RAM usage per account; if so, switch hosts or upgrade your plan
- Optimize images and code used on your site
- Manage caching settings – properly configured caches can significantly reduce resource requirements
Switch To A Default WordPress Theme
Switching to a default WordPress theme is one of the most effective ways to fix an HTTP 429 error – also known as ‘too many requests’ – in the ultimate guide to fixing this common server-side issue. As with any technical problem, there are numerous potential causes for too many requests errors; however, specific settings within certain WordPress themes can be a major factor. By switching to a standard WordPress theme, users can often reduce or eliminate these errors.
The process for making such a switch is relatively simple and straightforward; it begins by logging into the user’s hosting account where they should navigate to the file manager section. From there, the active theme directory must be selected from the list before clicking on “delete”. Once that step has been completed, users should select “add new” from the themes menu in order to upload the desired default WordPress theme. After installation finishes, all that remains is activating this new theme via the admin dashboard.
Disable The Really Simple SSL Plugin And Replace Your Internal Links
It’s possible to fix the HTTP 429 error by disabling the Really Simple SSL plugin and replacing your internal links. This approach can be effective in managing too many requests errors on a server. Here is how it works:
1) Disable the Really Simple SSL plugin – To disable this plugin, you need to access your WordPress Dashboard and select a folder called Plugins from the left-hand menu. From there, click ‘Deactivate’ next to the name of the Really Simple SSL Plugin.
2) Replace Internal Links – Once you have disabled this plugin, you can now replace your internal links with alternative versions that are free of any redirects or encoding issues. You should also ensure that all external URLs point directly to their source pages instead of passing through an intermediary URL.
3) Validate Your Work – Finally, validate your work by testing out each link on both desktop and mobile devices. If everything appears normal after making these changes, then you may have successfully resolved your too many requests error issue.
This method for fixing HTTP 429 errors has been proven useful in numerous cases and can help save time when dealing with similar technical issues.
Change Your Default WordPress login URL
WordPress users who are receiving an HTTP 429 error – too many requests – can change their default login URL to fix the problem. This guide provides a comprehensive overview of how to adjust the WordPress settings in order to eliminate the 429 issues.
By changing the default URL, users can reduce the number of requests and ultimately solve this particular error code. The process is relatively simple: access your admin panel, navigate to Settings > General, and then modify the WordPress address (URL) as well as the Site Address (URL). When finished, click Save Changes.
How To Avoid An Http 429 Error
First, it is important to understand some of the common causes of these errors. Too many requests sent from a single server or IP address can overload a server’s resources. Additionally, if the same request is repeatedly made from a client, the server may respond with an HTTP 429 error code instead of processing it. Finally, misconfigured caching settings on a web server may also contribute to receiving too many requests in one go and triggering an HTTP 429 error message.
To prevent such issues from occurring again, here are three tips:
1) Make sure your server’s resources are properly managed;
2) Utilize rate-limiting techniques when sending multiple requests;
3) Configure proper caching rules on your web servers.
By following these steps, you should successfully reduce the amount of traffic coming into your web application and thus avoid any HTTP 429-related problems.
All HTTP status codes by categories
When browsing the internet, you might run into various unexpected errors: HTTP 500, HTTP 503, HTTP 403, and — of course — HTTP error 429.
HTTP error codes such as 429 are a challenge because they often block you from accessing a website. To make sure you understand and can fix this problem, we’ll go over what “HTTP error 429: Too many requests” means and how to fix it.
HTTP Error 429 is an HTTP response status code that indicates the client application has surpassed its rate limit, or number of requests they can send in a given period of time. Typically, this code will not just tell the client to stop sending requests — it will also specify when they can send another request.
As a website owner, you’ll run into an error message from time to time. Some of these errors will be relatively simple to solve, while others will be more intricate. Take the HTTP error 429 for example.
Troubleshooting this error is complicated because it provides few details on what it is or how to solve it. You know something’s wrong and you need to fix it — but you’re not exactly sure what happened or why.
Causes of HTTP Error 429: Too Many Requests
A 429 response is not technically an error — it’s a response from a server, application programming interface (API), or plugin that tells the client application to stop sending requests because they simply don’t have enough resources to accept it at this time.
The client application usually refers to a website or app, but can also refer to individual users like the site admin or a site visitor or hacker.
A 429 error may appear the following ways, with or without the phrase “too many requests”:
HTTP error 429
HTTP code 429
HTTP error code 429
HTTP status code 429
HTTP response code 429
Response code 429
429. That’s an error.
429 server error
There was a problem with the server 429
Problem with the server 429
Here are some of the potential causes:
Repeated Requests to the Server
A 429 is often triggered by repeated requests. For instance, if a user is trying to access a page on your website too often in a short period of time, your server may send a 429 error.
Any website or app could experience this error, including Facebook, Etsy, Doordash, Venmo, YouTube, PayPal, Airbnb, Google Search Console, and — of course — WordPress websites (more on how to fix WordPress 429 errors below).
Brute-Force Login Attempts
In the case of a brute-force login attempt, in which a hacker repeatedly tries to log into your site, the 429 error code is an important security measure. It sets a rate limit for additional requests, preventing the brute-force attacker from being successful.
Server Resource Limits
You might also get a 429 error if your website is using up too many resources on a shared hosting server or service. If, for example, more than 50 requests are received from an IP address within one minute, PayPal Sandbox will block that IP for the next five minutes.
While the 429 response may seem punitive, it’s actually a protective measure against users intentionally or accidentally abusing server resources (or an API, plugin, or another service). It’s designed to prevent a backup or overflow of requests that would strain a server, or other service, that is meant to be shared and consumed by many websites and apps. So, by controlling the number and timing of requests, rate limits prevent problems before they arise.
If you are seeing the HTTP 429 error on your site for other reasons, you may need to reduce the number of server requests or API calls you’re making.
How to Fix an HTTP 429 Error
- Wait to send another request.
- Clear your browser’s cache.
- Flush your DNS cache.
- Implement exponential backoff.
Most of the steps below focus on avoiding, rather than retroactively fixing, an HTTP 429 error. Take a look.
1. Wait to send another request.
The simplest way to fix an HTTP 429 error is to wait to send another request. Often, this status code is sent with a “Retry-after” header that specifies a period of time to wait before sending another request. It may specify only a few seconds or minutes.
Here’s an example that asks the client to wait an hour before sending another request.
HTTP/1.1 429 Too Many Requests
<title>Too Many Requests</title>
<h1>Too Many Requests</h1>
<p>Only 100 requests per hour per logged in user is allowed on this website. Try again soon.</p>
2. Clear your browser’s cache.
If waiting doesn’t work, try clearing your browser’s cache, which stores your browsing data as well as requests. If you no longer have this data stored in your browser, your next request may go through.
To do so in Chrome:
Click CMD + Shift + Delete on Mac or Control + Shift + Delete on Windows.
The “Clear browsing data” analog pop up.
Click on the Advanced tab.
Select the time range and the data you’d like to delete.
Click Clear data.
To find instructions for your specific browser, click here.
3. Flush your DNS cache.
Flushing your DNS cache is another option if clearing your browser’s cache doesn’t work. Your computer’s DNS cache saves your domain name server requests so that it can load websites more quickly the next time you access them. Unfortunately, this may result in HTTP error 429 if you’ve made numerous requests before the DNS cache’s time-to-live naturally expires.
To clear your DNS cache on Mac, take the following steps:
Scroll down to the Utilities folder and click it.
In the Terminal window, enter the following command string: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Click enter, then input your admin password.
Click enter again.”
Find instructions for more operating systems here.
4. Implement exponential backoff.
If waiting, clearing your cache, or flushing your DNS cache don’t work, look for a “Retry-after” header again. If one is not sent and you don’t know how long to wait before trying, you should implement retries with exponential backoff.
Using this approach, you will not immediately repeat a failed request; instead, you will perform a series of retries with progressively longer wait times between each attempt. When the request is finally accepted, then you will know what wait time or rate is acceptable.
You can do this manually by using an exponential backoff calculator. Here’s how:
Access a calculator such as exponentialbackoffcalculator.com.
Input a time interval, such as 2 seconds.
Input the maximum number of retries or requests you’d like to make.
Input an exponential for subsequent requests.
Use a manual alarm or timekeeper to make new requests at the resulting timestamps.
Alternatively, if you’re a developer or advanced user, you can add code to implement this approach. For instance, you can use a framework like Celery that comes with a built-in exponential backoff module.
The steps discussed above are general fixes for the 429 “Too Many Requests” Error. If you have a WordPress site, then you may need a WordPress-specific solution.
How to Fix HTTP 429 Error on WordPress
If you’re getting an HTTP 429 error on your website, this can pose an issue to you as a WordPress administrator and also hamper your website’s user experience. Here are some tips you can follow:
1. Wait before re-accessing your website.
Your WordPress hosting provider may be receiving too many requests to load your website, resulting in an HTTP 429 error. This is especially likely if you use shared hosting, where your website is only allotted a limited number of resources on the host’s server.
In that case, be patient — the error will resolve on its own. If it keeps happening, however, you might want to upgrade to a dedicated hosting or VPS hosting plan.
You can also try clearing you cache, flushing your DNS cache, and trying exponential backoff during this step.
2. Hide or move your default WordPress login page.
Sometimes, HTTP 429 errors can arise due to cybersecurity attacks such as brute-force attacks on your WordPress login page. You can determine whether you’re under a cybersecurity attack in several ways:
Check your traffic sources using a WordPress traffic plugin or a tool such as Google Analytics. If you’re seeing a spike in traffic without a valid reason (such as a marketing or advertising campaign), then you may be under attack.
If the traffic source is from an unfamiliar country, that may also be a sign that someone from that location is trying to hack you.
If the traffic source is from one specific IP address, that may a sign that a single attacker is trying to login to your backend.
To move your default login page, you only need to change its URL. That can be easily done using the WPS Hide Login plugin.
Here’s how to use it:
Install the plugin through your WordPress admin dashboard.
Access the plugin’s Settings page.
Next to Login URL, add the new slug for your login page.
Click Save Changes.
Save the new URL somewhere for safekeeping — the last thing you want is to forget where to login!
3. Deactivate your plugins one-by-one.
If you’re still getting HTTP error 429 after waiting, clearing your cache, and checking for brute force attacks, it’s time to look at the next likely culprit: WordPress plugins.
WordPress plugins offer a wealth of functionality to WordPress website owners, but they can also cause performance issues, including HTTP errors such as 429.
Rather than deactivating them all at once, do so one-by-one so that you can isolate the culprit. Here’s how:
On your WordPress dashboard’s sidebar, tap Plugins > Installed Plugins.
Click Deactivate on the first plugin.
Check to see if this resolves the issue by accessing your website through an incognito window.
If not, deactivate the next one until all plugins are deactivated.
Activate them one-by-one once you’re finished.
4. Uninstall your custom theme.
If you’re using a custom WordPress theme from a marketplace such as ThemeForest or Envato, that may be the culprit. Make sure you save a backup of your website prior to deactivating the custom theme and temporarily installing a default WordPress theme.
5. Set your own throttling limit for any APIs.
An advanced technique you can try is to set a throttling limit if you’re using APIs on your website. Throttling is the process of limiting the number of requests an application can submit in a given amount of time. If this limit is exceeded, the server or API requests will typically be dropped or fulfilled with cached data.
While this approach is most often used by third-party APIs or platforms to prevent client apps from exceeding their limits, it can also be useful for restricting your own consumption of third-party APIs or server resources.
In fact, you can implement a stricter throttling limit for yourself to prevent going over the limits of a server, API, or other service you’re using. This is an especially good idea if you’re using a costly API, like the Twitter API, and don’t want to exceed your usage policy.
6. Contact your hosting provider.
Contacting your hosting provider is always an option for any error on your website, but it should be one of the last options you try.
If you’ve tried the steps above and are still seeing the 429 error, it’s possible that the cause originated from your server and not your website. It’s also possible that your host blocks requests from specific third-party services or platforms, like Google Search Console, which makes lots of requests to websites. By reaching out to your provider, they may be able to solve the issue or provide valuable insight.
How to Avoid an HTTP 429 Error
The most simple way to avoid this error is to reduce the number of requests made in a short period of time. The server is keeping track of how many requests per time unit you make and will enforce it — leading to a temporary block if exceeded. Some servers send this information in the header, on rare occasions.
And remember, receiving a 429 is not necessarily an error, it’s the server’s way of telling you your rate of requests is too high and not willing to accept those actions.
Though in some instances, the reason for the error may be your server rather than with your website. If that’s the case, nothing you will do from your side will help and you should contact your hosting provider for a resolution.
Resolving the HTTP 429 Error
An HTTP 429 error is common, but can be avoided by paying attention to rate limits set by your server, API, plugin, or more. If you exceed those limits, there are steps you can take to resolve a 429 error. By doing so, you’ll continue to provide visitors with a seamless user experience on your site.
This article was originally published in December 2020 and has been updated for comprehensiveness.