Procédure
This temporary error indicates that the site has made more requests than the shared hosting plan allows for a single IP address (the visitor’s IP or the robot visiting the site). The result is that the request reserve for this IP is empty and the rate is above the limit. The rate and the reserve depend on the plan.
Each LWS Linux plan benefits from a maximum request pool available per IP address. This pool only empties if you exceed the base rate; it will then drain as visitors to your site make requests and will automatically refill every second with a certain number of additional requests available.
| Plan | Base rate | Maximum pool per IP | Automatic addition each second |
| domain | 5 | 500 | 5 |
| LWS Perso | 20 | 500 | 20 |
| LWS Starter | 20 | 750 | 20 |
| LWS Standard | 20 | 750 | 20 |
| LWS Performance | 20 | 750 | 20 |
Each page of your site may use one or more requests each time it is displayed. To simplify, in general: 1 page displayed = 1 request.
If, when loading the page, it loads a module that itself makes an API call to load data, then that will be a second request made when the page is loaded, and so on.
Example:
On a domain plan, if a page consumes 2 requests each time it is displayed and that 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 pool will decrease by 2 requests each second: 10 - (2 x 6) = -2
Conversely, if this page is displayed only once per second from the same IP, your pool fills by 8 requests each second: 10 - (2 x 1) = 8
Consequence:
The number of available requests cannot exceed the maximum pool value per IP indicated for your hosting plan.
If your pool is completely empty, error 509 will be displayed for the user of the IP concerned until there are enough requests in the pool to display the desired page.
Internet users visiting the website from other IPs will not be affected by the temporary unavailability.
Solution 1: Identify request usage and try to reduce it if possible (cron task or robot making too many visits to your site, etc...)
Solution 2: Switch to a plan that provides a larger request pool and faster refilling given the high request usage of your site.
Solution 3: switch to a cPanel or VPS plan
Ask the LWS team and the community. Answers are published after moderation.