Error 509 - OL-RATE-PER-IP

Procédure

What does this error mean?

This temporary error indicates that the site has made more requests than the shared package allows for the same IP address (IP of the visitor or robot visiting the site). The consequence is that the pool of requests made by this IP is empty and the throughput is higher than the limit. The throughput and reserve depend on the formula.

How this error is generated :

Each LWS Linux package has a maximum available request basket per IP address. This basket is emptied only if you exceed the basic throughput, then emptied as and when visits to your site consume requests and automatically refilled every second with a certain number of additional requests available.

Formula Basic bandwidth Maximum basket per IP Automatically added every second
domain 5 1000 5
LWS Personal 10 2000 10
LWS Starter 10 2000 10
LWS Standard 10 2000 10
LWS Performance 10 2000 10

Each page on your site can use one or more queries each time it is displayed. To simplify, in general: 1 page displayed = 1 request.

If, when the page is loaded, it loads a module which itself makes a call to an API to load data, then a second request will be made when the page is loaded, and so on.

Example:

On a domain formula, if a page consumes 2 requests each time it is displayed and this page is displayed 6 times per second from the same IP (if several people are browsing your site with the same Internet connection, for example), then your shopping basket will decrease by 2 requests each second: 10 - (2 x 6) = -2

Conversely, if this page is only displayed once per second from the same IP, your basket will fill up with 8 requests every second: 10 - (2 x 1) = 8

Consequence:

The number of available requests cannot exceed the value of the maximum basket per IP indicated for your hosting package.

If your basket is completely empty, the 509 error will be displayed for the user of the IP concerned until there are enough requests in the basket to display the desired page.

Users visiting the website from other IPs will not be affected by the temporary unavailability.

What can be done to resolve the problem?

Solution 1: Identify the request consumption and try to reduce it if possible (cron job or robot making too many visits to your site, etc.).

Solution 2: Change your package to one that allows you to benefit from a larger basket of queries and a faster fill rate, given the large number of queries your site is consuming.

Solution 3: Change to a cPanel or VPS package.

How can we help?

Rate this article :

This article was useful to you ?

Article utileYes

Article non utileNo

Vous souhaitez nous laisser un commentaire concernant cet article ?

Si cela concerne une erreur dans la documentation ou un manque d'informations, n'hésitez pas à nous en faire part depuis le formulaire.

Pour toute question non liée à cette documentation ou problème technique sur l'un de vos services, contactez le support commercial ou le support technique

MerciMerci ! N'hésitez pas à poser des questions sur nos documentations si vous souhaitez plus d'informations et nous aider à les améliorer.


Vous avez noté 0 étoile(s)

Similar articles

0mn reading

Cloudflare Error 524 : A timeout occured

3mn reading

How to correct a 500 error on your site with LWS Panel

10mn reading

How do I correct HTTP error codes?

0mn reading

404 error, what it is and how to correct it


Ask the LWS team and its community a question