Web servers use HTTP status codes to communicate with clients when serving website content. There are many variations, from status codes 3xx that identify the redirection processes to the 4xx codes which indicate client-side errors.
One of these HTTP codes is the 429 Too Many Requests. As its name suggests, this code appears when someone repeatedly accesses a website and exceeds the speed limit. In most cases, this error will lock you out of the admin panel and make the site inaccessible.
With this in mind, this article will give you six effective solutions to diagnose and resolve a 429 error on your website. First, let’s start with more detailed information about this HTTP error.
Error code429 Error Too Many Requestsbug typeclient errorVariations of the errorError 429
Http429
429 Too many requests
Error 429 (Too many requests)Causes of the errorOverload of requests to the server
Distributed Denial of Service (DDoS) attack
brute force attacks
What is the 429 Too Many Requests error?
The HTTP 429 error is not technically an error, but rather a response sent from a web server or a application programming interface (API) when a user has sent too many requests to the server in a given time.
Depending on the browser you are using, the error message may appear in these variations:
- Error 429
- Http429
- 429 Too Many Requests
- Error 429 (Too many requests)
However, web servers have limits. When they don’t have enough memory to process the requests, the 429 error occurs.
In addition, the HTTP 429 error can also appear in response to security measures. Too many requests may indicate or .
HTTP 429 will block the suspected user or IP address to protect the website. In this way, it can prevent hackers from entering your login page and block bots from using your server resources.
What causes the 429 error?
As mentioned above, the HTTP 429 error occurs when the server detects too many attempts in a short period of time. This could be due to a user trying to log in with incorrect credentials or an attacker trying to sabotage your website.
Whenever this situation occurs, the system will trigger a rate limiting feature, triggering the HTTP 429 error.
Rate limiting is a strategy used by APIs to limit network traffic when it detects an excess of the maximum number of activities within a specified time frame. This feature helps prevent malicious activity from bots or hackers and reduces stress on the web server.
In addition to displaying the HTTP code, the error message often includes additional details along with the cause of the error, such as:
HTTP/1.1 429 Too Many Requests Content-type: text/html Retry-After: 3600
In the example above, the header Retry-After specifies the time limit during which the user is forced to stop sending requests.
Normally, the 429 error goes away after a while. However, if caused by a malicious attack, the error can make your website unavailable and prevent you from accessing the WordPress admin area.
6 Ways to Fix Error 429 Too Many Requests
In the following sections, we’ll walk you through the six methods for diagnosing the 429 error, its most common causes, and steps to fix it.
1. Empty the cache
The browser cache stores website files and account information on the client side for a better browsing experience. With the data stored in the cache, the browser can load the web page faster the next time you visit it.
However, when this data accumulates, it can cause the 429 error.
Therefore, the first step is . To illustrate, we will show how to do it in Google Chromealthough the process is similar with any other browser:
- Click the three dots symbol in the top right corner of Google Chrome and then select Setting.
- Navigate to settings Privacy & Security Y select Clear browsing data.
- From there, check the options Cached files and images Y Cookies and other site data. Next, open the dropdown menu to select the time range.
- click on Delete data and restart Google Chrome to complete the process.
Please note that clearing cache data will increase load time as the browser will have to re-download the content from the website.
Furthermore, clearing the cache will also clear the history of the website and reset the custom settings. To avoid this, make sure to and revert to once the process is finished.
If your browser’s cache was causing the 429 error, performing the steps above will resolve the issue. However, if the error persists, try the next method.
2. Check order usage in hPanel
Request usage refers to the number of HTTP requests sent. Checking your website’s order usage helps monitor incoming traffic. This makes it easier to point out when an unusual spike in traffic occurs.
users can check HTTP requests by accessing the hPanel control panel. go to Services – Plan History.
In this section, you will find several metrics related to the use of the website, such as:
- CPUs: the percentage of the central processing unit used by your site.
- Memory: the total memory used by your hosting account to process requests.
- Processes: the number of processes running on your hosting account.
- Input processes: the number of processes used to fulfill requests from your website.
- Total requests: shows HTTP and HTTPS requests from all hosting accounts.
- Unique IP addresses: tracks the different IP addresses that access your website.
- Bandwidth: data transferred in a specific period of time.
These metrics can help identify if your website is at risk of cyber threats.
3. Disable all WordPress plugins
When troubleshooting the 429 too many requests error on a WordPress website, consider the possibility of conflicting plugins. This can crash your website or cause it to malfunction. In particular, pay attention to all third-party plugins, as they might not be reliable.
If the 429 error persists after performing the two steps above, try temporarily disabling all WordPress plugins.
To do this, open the folder wp_content in your root directory. You should see a folder called plugin. Proceed to rename the folder, for example, plugins-disable.
Try to scan your website, if it comes back to normal with no active plugins, this means a faulty plugin was causing the problem.
Continue renaming the directory plugin to its original name and proceeds to activate the plugins one by one. This way, you will be able to detect the plugin that is causing the 429 error.
Once you have found the faulty plugin, try updating it and see if it fixes the problem. If not, you may need to disable it and install a new plugin.
4. Switch to a default WordPress theme
Poorly coded WordPress themes can also cause conflicts. Although not a common cause, a theme can conflict with certain plugins and send too many requests to the web application, causing the 429 error.
The easiest way to solve this problem is to change your current theme to a default WordPress theme. If you can’t access your WordPress dashboard, follow the steps below to change the theme via phpMyAdmin:
- Go to your File Manager and open the file wp-config.php. Inside it, locate the name of your site’s database.
- Close the file and open your phpMyAdmin. Select the name of the corresponding database and choose the table wp_options of the list.
- There, find the rows template Y style sheet – are usually found on the second page.
- Simply double click the option_value of each row and edit the value to the default theme name, eg twenty twenty one.
Once you’re done, go back to your site to see if this fixed the issue. Alternatively, remove the previously active theme and reinstall it. However, if the error persists, the best option is to remove the theme completely.
5. Restore the site from a backup
Having one can protect you from data loss, malware infections, and security breaches. By restoring a backup of the site, you can revert any changes that might cause HTTP 429 errors and return the website to normal.
The following are the steps to restore your website and resolve the HTTP 429 error:
- Access your hosting control panel. users can access the control panel of hPanel and navigate to Files – Backup copies.
- Clicking on it will bring up various types of backups saved on the server. For websites powered by WordPress or others, you’ll need to restore both the website files and the .
- Click on the button file backups and then click show files. If you want to restore the entire site, choose the folder public_html and click Restore files.
- Next, restore your database. Select the option Database backupschoose the database to restore and click Show databases.
- A list of available backup dates will appear: choose the desired date and click Restore.
- The system will begin processing your request and will notify you once it is complete.
After the restore is complete, all changes made after the chosen restore date will be reverted. This will restore your site to a stable state and remove the HTTP 429 error.
6. Change WordPress Default Login URL
Every WordPress website has a default login URL, such as wordpresswebsite.com/wp-admin or wordpresswebsite.com/wp-login.
However, due to its generic nature, this default URL is prone to malicious attacks, increasing the chances that your website will experience 429 errors.
An easy way to change your login URL is by installing the plugin. The plugin creates an alternate login page to prevent hackers from entering your website.
To install the plugin, navigate to your admin panel, choose Plugins > Add Newand write the name of the plugin
Once you have activated the plugin, go to Configuration – WPS Hide Login and scroll down until you see the field Login url.
From there, feel free to customize your alternate login URL. Once done…