Much like most other software, WordPress also has its flaws. Occasionally running into an error is normal for most WordPress users. But, don’t blame WordPress for the 429 Too Many Requests error.
This particular WordPress error can surface for several different reasons, sometimes it can occur by the user’s own faults but it’s not WordPress’ fault. Never the less, we’re going to help you fix it.
If you’ve encountered the 429 Too Many Requests error while using WordPress, don’t worry it can be fixed. In this post, we’ll walk you through three simple methods for fixing this error and give you a few tips on how to avoid it in the future.
In order to figure out the cause behind the 429 Too Many Requests error, you need to understand how WordPress works.
WordPress is a CMS (content management system) that uses PHP language for performing its functions. Whenever you perform a task, make a change, or add something new to your website, WordPress run PHP scripts to execute those tasks. When you make a change and WordPress execute a PHP script it sends a “request“ to your website server to perform the requested function. That’s how most parts of WordPress work.
The 429 Too Many Requests error occurs when WordPress tries to send too many requests to the server. This error system is in place to protect your server from DDoS attacks, which hijacks websites to do hackers’ bidding. It can also be caused by a third-party plugin or a poorly coded theme.
There are a few simple methods you can try to find the main cause behind the 429 Too Many Requests error and fix it. We’ll walk you through them, step by step.
First, make sure that you aren’t using any outdated plugins or themes. Especially if you’re using pirated themes or plugins, you should get rid of them immediately because those are usually the main culprits of this error.
Let’s get started.
Most modern WordPress plugins are service-based plugins that function by connecting to a third-party API. Such plugins can be the main reason for the 429 Too Many Requests error.
To figure out which plugin is causing the error, you need to disable all of the plugins and then re-enable them one at a time until you encounter the error again.
To disable plugins, simply login to your WordPress dashboard and go to Plugins page. Then select all active plugins and choose Deactivate from the Bulk Actions drop-down menu.
If you don’t have access to your WordPress admin dashboard, follow the steps below to disable the plugins from the server.
You can use an FTP client app to login to your server. Although, we’re going to use CPanel to access the server since it’s available to everyone. The process is basically the same so use any app you’re comfortable with.
To access your website’s CPanel, type /cpanel at the end of your website URL (eg: yourwebsite.com/cpanel). Then enter the server username and password given to you by your web host. If you don’t remember the login details, search for it in your web host’s welcome email.
On the CPanel dashboard, you’ll find an app called File Manager. Open this app to access your website files.
Navigate to the public.html folder. Then open the WP-Content folder. You’ll find the folders for your WordPress plugins and themes inside this folder.
To disable all the plugins on your website, all you need to do is to rename the Plugins folder.
Right-click on the folder and choose Rename. Then type in a name like plugins-bad.
Now create a new empty folder and name it “plugins”.
Visit your website and see if it fixes the problem. If the issue is fixed, then it’s likely caused by a plugin.
It’s time to figure out which plugin causes the issue.
Go back to your server and to the WP-Content folder. Then delete the empty “plugins” folder you created earlier. And rename your “plugins-bad” folder back to “Plugins”.
This will restore all your plugins back on your website. Don’t worry, all the plugins will be deactivated. All you have to do now is to login to your WordPress dashboard and re-activate the plugins one by one until you find the culprit.
Poorly coded and outdated WordPress themes can also be the cause of 429 Too Many Requests error. It’s common among websites that use free themes as well. Try changing your active theme to see if it fix the issue.
Login to your WordPress admin dashboard and go to Appearance >> Themes. Then activate the default WordPress theme.
If you don’t have access to the admin dashboard, follow the same steps described in the previous method to disable themes from the server. Only this time rename the Themes folder instead of the Plugins folder.
If this fixes the problem, then it’s time to upgrade your website theme.
If the above methods didn’t work, then it’s time to seek professional help. Sometimes, the 429 Too Many Requests error can be caused by server-side issues, the services they use, and third-party web apps as well.
Reach out to your web host’s technical support team and ask them to check your website. Depending on the web hosting service you use, they will even offer to fix the issue for you, even if it’s caused by your website.
The 429 Too Many Requests error is a terrible issue that can eat up your server resources and even break your website. Take the necessary steps to avoid this problem in the future.
First, make sure that you’re using a solid and high-quality web hosting service. Using a managed WordPress hosting service is highly recommended as they provide you with tools for protecting your website from DDoS attacks and routine website backups.
Avoid using outdated plugins and theme. And never even think about using pirated themes or plugins. Those themes always come with secretly injected scripts that will take advantage of your website and server resources.
Also, try installing a free malware scanner plugin on your website to keep your website safe from hackers.