Facing Error 429 on a webpage: What should you do?

Introduction

All websites run into bugs or errors that are hard to diagnose. There is often little information in the error itself, so you cannot pinpoint the cause. One such error is 429 Too Many Requests. There is no mystery to its causes, fortunately. There are several possible problems, however, so you’ll often have to try several fixes before your issue is resolved.

We know how frustrating experience it is when you need to visit a webpage in order to get your things done and unexpectedly the webpage throws an error page in front of you. That’s why here in this article we will briefly discuss what the error 429 is all about, what causes this error and how can we fix it in the simplest possible way.

All in all, here in this article, this 429-error message is explained in a simple manner that can be understood by a layman.

 

What is error 429!?

A user can send too many HTTP requests in a short period of time, resulting in the HTTP 429 error. Use of the 429-status code is intended for applications that place rate limits. Basically, HTTP status code 429 (Too Many Requests) is a server-sent client error that signals you have reached the limit.

In spite of the fact that rate limiting may seem unwelcome at first, most consumable APIs use this restriction as a safeguard. A rate limit prevents intentional abuse as well as accidently exploiting services during development. You’ve probably noticed that the water in a funnel backs up when poured too rapidly. The purpose of rate limiting is to prevent this by stopping requests from flowing before they create a problem.

From technical point of view, a 429 response is not an error, but rather a message from a server, API, or plugin informing the client that they do not have sufficient resources to accept the request at this time. An application client is usually a website or app, but can also be a user, such as an admin or a website visitor.

The purpose of this is to prevent a backup of requests or an overflow of services for servers that are shared and accessed by dozens of websites and apps.

It’s completely upon the website developer to decide how to design and display the 429-error message. That means there is no fixed specific error message text which will be displayed once you encounter a 429 error.

You might receive the HTTP 429 error in the following possible pattern:

  • A 429 error has occurred
  • Error 429
  • HTTP 429
  • Error 429 (Too many requests)
  • An error occurred while trying to load [URL].
  • 429 – Too many requests
  • There is an error 429 too many requests
  • Too many requests HTTP 429

429 Errors and their causes:

In technical terms, an Error 429 is a client-side error, implying that given the website you are visiting has rate-limiting scheme, in a very short amount of time you have sent numerous request that’s why you are not allowed to visit the website for few moments from now.

It doesn’t matter what the error message says, what it means is the same – someone or some code is overloading your server. Your server may initiate rate-limits when it detects that a user agent tries to access a page too frequently within a short span of time. Typically, this happens when a user (or malwares) repeatedly logs onto your website. Alternatively, server-side cookies can also be used to identify users. The number of requests may also be calculated per request, across several servers, or across your entire network.

Error 429 may be caused by a variety of factors, so understanding what can trigger it is crucial for us. If you’ve been trying to access a page too many times, the error should go away on its own a short time later. You may find that your web host has a setting that limits access for a few minutes following suspicious behavior. So, if it’s the case, no need to worry!

In the case of a persistent error, it could be a symptom of a malicious attack or a third-party service that is overloading your server. In such a case, you might have to dig deep to fix it.

429 Not Found Error: How to Fix It

  1. Rogue plugins can often be the cause of persistent 429 errors.  There are many plugins that may trigger error 429, for instance the security plugin. Disabling all plugins on your website is the fastest way to figure out if one of them is causing HTTP error 429.  In the case the error persists after that, try a different solution, and if it no longer exists, begin to find the culprit.
  2. Switch to a default theme on WordPress.  It’s possible that your active theme is responsible for error 429. A complex theme using API keys is more likely to have caused this issue. As WordPress needs an active theme to function properly, it will choose one of the default themes. The error should be gone after switching to your default theme, so you should notice some changes in your website. The next step is to re-install the theme or to restore its original name if your theme already exists.

You might need to go back to an older version of the theme or change themes if the error persists.

  • It is common for websites to encounter the 429-error due to excessive brute-force login attempts. If you want attackers to be unable to find your WordPress login page, you can simply change the URL so they cannot find it at all.

In the default configuration, your login page can be accessed through mywebsitename.com/wp-admin. Any common man on the web will know exactly where to find it, so it’s not only easy to remember but insecure as well. It is easiest to conceal your login information by using a plugin such as WPS Hide Login.

The only other way to update your WordPress login URL is manual, but we advise you not to do so because it requires making significant changes to your site’s core files.

  • In today’s world, your entire website should be secured with HTTPS. Your website will be more secure with this protocol than it would be with HTTP, and it will even benefit your site’s SEO. A .htaccess redirect can be used to enforce HTTPS use, or a plugin can do it. Among the top choices is Really Simple SSL.

A key benefit of this plugin is that it enables HTTPS to be used for your entire site with just a few clicks.  There are times, however, when it may lead to erroneous results, like a 429 error for instance. Your first concern will be the plugin itself. In WordPress’ admin area, you can simply click Deactivate to turn off Really Simple SSL – if you have access, of course.

Due to the 429 Too Many Requests Error often preventing you from logging into your dashboard, you may need to disable the plugin manually using an FTP client to get access to it. The error 429- too many requests be resolved once the Really Simple SSL plugin is removed.

Conclusion:

It is common for HTTP 429 errors to occur. However, you may be able to avoid them by paying a little more attention to rate limits set by your server, APIs, plugins, and so on. The 429 error can be resolved by following the steps introduced in this article if you exceed those upper limits. As a result, visitors will experience your site seamlessly.

As a visitor, A website error is always a frustrating experience. When it comes to errors, those with numerical codes offer at least enough information to begin fixing them. It will be evident, if you obtain a 429 Too Many Requests error, that there is something generating too many requests on your server. You now need to figure out what caused the problem.

Leave a Comment

Your email address will not be published.