Troubleshooting · Troubleshooting
How to Fix the 429 Too Many Requests Error in WordPress
Short answer
A 429 Too Many Requests error means a server, host, or security layer received too many requests from one source in a short time and refused the extra ones. Wait for the Retry-After period to pass, then find the source, which is often repeated login attempts, bot traffic, or a plugin sending requests in a loop. Fix that source instead of turning off your security rules, and check your logs to confirm the 429 responses have stopped.
Key takeaways
- A 429 error is a rate limit, not a broken page, and it clears when the request rate drops.
- The Retry-After header tells you how long to wait before you try again.
- Repeated login attempts, bots, and plugin loops are the most common causes on WordPress sites.
- Cloudflare can block a login flood for 15 minutes after 5 POST requests in 5 minutes.
- A 429 from WooCommerce.com or another outside service does not mean your own site is down.
What does the 429 Too Many Requests error mean in WordPress?
A 429 error means your site, host, or security layer received too many requests from one source in a short time and refused the extra ones.
The HTTP 429 Too Many Requests status code signals rate limiting, as MDN explains in its HTTP status reference (checked November 2026). The server is still running, but it is asking the client to slow down.
The response may include a Retry-After header that states how long to wait. MDN gives an example value of Retry-After: 3600, which means 3,600 seconds, or 60 minutes, before requests are allowed again for that client.
Cloudflare gives the same reading in its Error 429 support page (checked November 2026). It states that the server may include a Retry-After header to specify when the client can try again.
What causes a 429 error on a WordPress site?
The most common causes are repeated login attempts, bot traffic, a plugin that sends requests in a loop, and a rate limit set by your host or Cloudflare.
Kinsta lists bots and scrapers as the most common cause in its troubleshooting guide for client errors (checked November 2026). Automated traffic that crawls many pages fast can trip a limit in seconds.
Plugins and integrations are the next cause to check. Kinsta notes that tools that sync, import, or check your site can send bursts of requests, for example to admin-ajax.php or the WordPress REST API.
A real traffic spike can also trip a limit. If many visitors arrive at once, or one office shares a single IP address, that IP can look like one heavy client.
| Cause | Where it shows up | First check |
|---|---|---|
| Login attacks | wp-login.php | Failed login count in your security log |
| Bots and scrapers | Many pages at once | Top IPs and user agents in your logs |
| Plugin loop | admin-ajax.php or /wp-json/ | Requests per minute from one endpoint |
| Cloudflare rule | Whole site or one path | Cloudflare Security Analytics events |
| Outside service | Admin update checks | The service status and its own limit |
How do you tell who is sending too many requests?
Check the time, the page or endpoint, and the source IP in your host logs or security dashboard before you change any setting.
On Kinsta, each limited request is recorded in error.log as limiting requests, excess: ... by zone "phpzone", according to Kinsta's troubleshooting guide for client errors (checked November 2026). That line names the limit zone that was hit.
Look for one IP, one user agent, or one URL that repeats far more than the rest. A single IP hitting wp-login.php hundreds of times in a few minutes points to a login attack. A single IP crawling every page points to a bot.
Check whether the 429 appears on one page or on every page. A 429 on one path points to a limit on that endpoint. A 429 on every page points to an IP or account limit, or to a limit on the whole site.
Note the exact time and the IP address involved. Your host needs both to find the matching rule, so write them down before you contact support.
How do you fix a 429 error caused by login attacks?
Wait for the lockout to end, then add a login limit at the edge or with a plugin so repeated guesses stop reaching WordPress.
WordPress core does not limit login attempts on its own. The WordPress Brute Force Attacks handbook (checked November 2026) advises you to rate limit login attempts at the edge, with a firewall or CDN, or at the web server.
Kinsta bans IPs with more than 6 failed login attempts in a minute, as Kinsta states in its login URL guide (checked November 2026). If your host already does this, your own failed logins can also trip it, so wait before you try again.
Follow these steps in order:
- Wait for the
Retry-Afterperiod or lockout to pass, then try once from a different network if you can. - In your WordPress dashboard, go to Plugins, then Add New, and install Limit Login Attempts Reloaded.
- Open the plugin settings and set a low retry limit and a lockout time, then save.
- Add a human check to the login form, such as Cloudflare Turnstile, using our guide to Cloudflare Turnstile on WordPress.
Limit Login Attempts Reloaded has more than 2.5 million active installations, according to its WordPress.org plugin page (checked November 2026). It blocks an IP address or username after a set number of failed retries, and its lockout times are adjustable.
The WordPress handbook also warns that xmlrpc.php is a frequent brute force target, above all the system.multicall method. If you do not use XML-RPC, disable it. If you do use it, restrict it and rate limit it hard.
How do you fix a 429 error caused by a plugin or integration?
Find the plugin that sends the extra requests, slow it down or turn it off, then check that the request rate falls.
Start in your dashboard under Plugins, then Installed Plugins. Deactivate the plugin you installed or updated most recently, then load the page that showed the 429 error once.
If the error clears, reactivate your plugins one at a time and test after each one. The plugin that brings the 429 back is the source. This slow test beats deactivating everything at once, because it names the cause.
If you cannot reach your dashboard, rename the plugin folder through your host file manager to turn all plugins off, then rename it back and reactivate plugins one at a time. Do this only after you have a backup.
For integrations, reduce how often they run. Kinsta advises you to set sync and import tools to send requests in smaller batches, as stated in its troubleshooting guide for client errors (checked November 2026). A tool that checks your site every minute can often run every 15 minutes instead.
Also check scheduled tasks. A stuck cron job or a backup job that runs too often can send the same requests again and again. Pause the job, then watch the logs.
How do you fix a 429 error caused by Cloudflare rate limiting?
Open your Cloudflare rate limiting rule, find the threshold that real visitors trip, and raise or narrow that rule instead of deleting all protection.
Cloudflare blocks further requests with an HTTP 429 response once an IP address passes a rule threshold, and the response includes a Retry-After header, as Cloudflare states in its rate limiting docs (checked November 2026). The block lasts until the time window resets.
Cloudflare offers a one click login guard. Its rate limiting guide states that Protect your login blocks the client for 15 minutes when it sends more than 5 POST requests within 5 minutes.
To create or edit a rule, follow the steps in Cloudflare's guide to creating a rate limiting rule (checked November 2026):
- In the Cloudflare dashboard, go to the Security rules page.
- Select Create rule, then Rate limiting rules.
- Enter a name in Rule name and set the path, such as
/wp-login.php. - Under When rate exceeds, set the request count and the time period.
- Under Then take action, pick Block, set the Duration, then select Deploy.
If real visitors are blocked, narrow the rule to one path, such as the login page, instead of the whole site. Raise the threshold a little, shorten the block time, and test again. Our guide to setting up Cloudflare for WordPress covers the dashboard steps in more detail.
Cloudflare also lists its own API limits on its Error 429 page (checked November 2026). The client API allows 1,200 requests per 5 minutes per user or account token, and 200 requests per second per IP. Those are Cloudflare API limits, not limits on your site pages.
For wider firewall settings, see our guide to Cloudflare WAF rules for WordPress. Keep the rate limit rule separate from your other firewall rules so you can change one without touching the rest.
How do you fix a 429 error from an outside service?
Check whether the 429 comes from the outside service, not from your site, then slow down the calls to that service.
A WordPress.org support thread about WooCommerce shows this pattern clearly. The https://woocommerce.com/wp-json/helper/1.0/update-check endpoint is rate limited by WooCommerce.com, and shared hosting IPs can hit that limit together, as the WordPress.org support thread explains (checked November 2026).
That limit does not affect your store front end or checkout. It only affects extension update checks and licence syncing, and it clears on its own once the request volume drops.
To reduce it, stop forcing update checks by hand. Do not click Check again many times in a row, and do not run wp plugin update on a tight loop. Make sure only one cron system runs, and ask your host to run server cron if WordPress cron runs twice.
If the 429 names a different service, read that service docs for its limit and its reset time. Slow your calls to fit it, and cache the answers where you can. Raising a limit on your own site will not fix a limit set by someone else.
How do you know the 429 error is fixed?
Load the page that failed, wait out any Retry-After period first, and confirm that the page loads and the 429 count in your logs falls to zero.
Start with one load, not a burst of refreshes. Refreshing many times in a row can trip the same limit again and make a fixed site look broken.
Check your logs again after 10 minutes. The IPs and endpoints that filled the log should be quiet, and new 429 lines should stop. If the same IP still floods the log, the source is still active.
On Kinsta, requests that return a 429 do not count toward plan usage, as Kinsta states in its analytics docs (checked November 2026). A falling 429 count is a real sign of progress, not a billing change.
Test the exact action that failed before, such as logging in or saving a post. If it works once and then works again after a short wait, the fix holds.
When should you contact your host about a 429 error?
Contact your host when the logs point to a server limit, when you cannot find the source, or when real visitors are still blocked after you fixed the cause.
Kinsta asks you to contact support with the time of the errors and the IP address or tool involved, as stated in its troubleshooting guide for client errors (checked November 2026). Send the exact time, the IP, the URL, and the error.log line if you have it.
Ask your host three things: which limit was hit, what the threshold is, and whether it can be raised or scoped to one path.
A host limit on PHP workers or requests per minute is not the same as a plugin limit, and only the host can change it. Our guide to reading a hosting plan CPU and RAM limits helps you read the numbers in the reply.
Also contact your host if the 429 started right after a plan change or a move to a new server. A new server can carry stricter default limits than the old one.
Do not ask the host to turn off all rate limiting. A site with no limit is open to login floods and bot floods, and the 429 will return in a worse form.
What mistakes should you avoid?
Do not refresh the page many times in a row, because each refresh adds requests and can extend the block.
Do not turn off your firewall, your login limit, or your Cloudflare rules to make the error go away. That removes the guard that caught the flood, and the flood will return.
Do not raise every limit at once. Change one rule, test it, and watch the logs. If you change five rules at once, you will not know which change worked.
Do not blame your theme first. A theme rarely sends bursts of requests, while login attacks, bots, and sync plugins do. Test plugins and traffic sources before you switch themes.
Do not ignore a 429 that only appears in your admin area. Admin update checks, cron jobs, and sync tools can hit outside limits that your visitors never see, and they still need a fix.
Frequently asked questions
How long does a 429 error last in WordPress?
It lasts until the rate limit window ends, which can be seconds, minutes, or an hour. The Retry-After header states the wait when the server sends one, and MDN gives 3,600 seconds as an example. If the source keeps sending requests, the block can renew, so you must also stop the flood.
Is a 429 error the same as a 403 error?
No. A 429 means you sent too many requests too fast and should slow down, while a 403 means the server refuses access to that page. A 429 is temporary and clears when the rate drops. A 403 stays until the permission or rule changes, so the two errors need different fixes.
Can a plugin cause a 429 error even if visitors see the site fine?
Yes. A plugin can send bursts of requests to admin-ajax.php or the REST API while visitors browse normal pages without trouble. Sync, import, backup, and security tools are common sources. Deactivate the newest plugin first, test once, and reactivate plugins one at a time to find it.
Should I clear my browser cache to fix a 429 error?
Clearing your cache rarely helps, because a 429 is a server side rate limit, not a stale page in your browser. Wait for the Retry-After period, then load the page once. If the error returns at once, check your logs for the source IP and endpoint instead of clearing the cache again.
Does a 429 error hurt my search rankings?
A short burst of 429 responses is a signal to crawlers to slow down, not a sign that your pages are gone. The risk grows if the same URLs return 429 for days, because crawlers may stop visiting them. Fix the source fast, keep the 429 period short, and check that your pages load normally again.
What should I tell my host when I report a 429 error?
Send the exact time the errors started, the IP address involved, the URL or endpoint that returned 429, and the matching log line if you have one. Ask which limit was hit and what its threshold is. Those four facts let support find the rule in minutes instead of guessing.
Sources
- 429 Too Many Requests MDN Web Docs
- Error 429 Cloudflare Support
- Create a rate limiting rule in the dashboard Cloudflare WAF Docs
- Troubleshooting - Client Errors Kinsta Docs
- Brute Force Attacks WordPress Developer Resources
- Limit Login Attempts Reloaded WordPress.org
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
