The “Error 429 (Too Many Requests)” in WordPress tells you exactly what caused it. Well, unless you get a shortened format such as “429 error” or “HTTP 429”. But since it occurs at the user login page on your website or the WordPress Admin Dashboard page, you can remember your most recent set of actions. The requests can be innocent, such as repeated incorrect logins by users or admins or a malfunctioning plugin. Malicious reasons include bots trying to brute-force their way in or cause a Denial of Service (DDoS). Regardless of the source, here’s how to fix the WordPress 429 Too Many Requests error.
1. Change the WordPress Admin Section login URL
Repeated login attempts in a short time are the likely cause of the WordPress 429 Too Many Requests error. For that reason, you should move on from the default WordPress Admin Section address (yourwebsite.com/wp-admin). To block DDoS attacks or bots trying to log in, follow our guide on how to change the WordPress login URL. Afterward, simply access the WordPress Admin Section using the new URL, and don’t share it with anyone but the people who require it.
2. Disable your SSL WordPress plugin
No dice yet? Let us ask you this. Did you use a WordPress plugin to make a switch from HTTP to HTTPS for security? While it’s quick and easy, this method to transition your website to SSL can be the culprit. To check if the plugin (for example, Really Simple SSL) is the reason the 429 Too Many Requests error appears, you should deactivate it. Since the error obviously locks you out of the WordPress Admin Section, you should access your WordPress website via FTP. Then, find the headline Fixing the problem if the plugin caused it in our “Are you sure you want to do this” error fix guide. If nothing changes, enable it again.
Deactivating the SSL plugin fixed the problem?
Don’t give up yet, try a different plugin for SSL. You can also implement an SSL certificate for WordPress manually, which is the preferred way. We’ll make a detailed guide soon, so stay tuned. In the meantime, you should revert any URL redirects. Also, change the WordPress website URL back to HTTP. We outlined two ways to do it under Method 4 in our guide on fixing WordPress keeps logging out the problem.
3. Disable all WordPress plugins temporarily
If disabling the SSL plugin didn’t work, another one might have caused the 429 Too Many Requests error. While you’re there, rename the entire plugins folder to, for example, plugins.old, refresh your website, and try to log in. If the error goes away, slowly enable plugins one by one until you find which one triggers it. Afterward, find an alternative or contact the plugin developers.
4. Deactivate your WordPress theme
Troubleshooting showed plugins are fine? A faulty script, link, or resource in the active WordPress theme can overload the server with too many requests as well. While you have FTP access, rename your current theme folder the same way as with the plugins one. Unless you disabled default WordPress themes, one of them will automatically be enabled instead. No difference? Restore its original name and carry on.
Solved the WordPress 429 Too Many Requests error?
If so, you can delete your WordPress theme and find an alternative that doesn’t produce the error. However, you likely invested time, effort, and/or money into customizations. If so, here’s how you can proceed:
- Try to find the cause yourself. We don’t recommend it. It can take hours of your time while producing no results.
- Get in touch with theme developers. They might be able to push an update or find a solution if your problem is unique.
- Hire a professional. Pick a proven organization or a freelancer. It’ll cost you, but you get to keep your current theme.
- Follow the method below. This is a great choice if you are on a budget and aren’t sure you’ll keep the current theme.
5. Contact your hosting Customer Support
Reaching out to your hosting Customer Support is a free way to solve the WordPress 429 Too Many Requests error. It’s also easy and ideal if you don’t want to make the problem bigger by experimenting. Send a message via e-mail or their 24/7 Live Chat or open a ticket in their cPanel. On the other hand, it isn’t guaranteed to work. Sometimes they’re unable to help, other times it’s not their responsibility.