Error 429 too many requests

It seems 429 errors are indicators of rate limiting:

429 Too Many Requests

I found an user that was having similar issues with loader.io and Cloudflare, where Cloudflare was responding with a 429 error due to apparently the limited number of IP addresses the service uses to generate the requests:

How to whitelist load testing IPs

The next questions I wanted answered were: where is rate limiting happening and how is it configured? After some more research I found that rate limiting is most likely located at the web server level and it's mostly done it's done via two methods:

• Based on the rate of requests per user agents used
• Based on the rate of requests per IP address

I found some articles on how to solve the 429 error by showing you how rate limiting is configured, which will hopefully assist you on making the necessary changes to pass the tests from loader.io:

• How to Resolve Rate Limited Requests (429 Too Many Requests)
• How To Resolve ‘Too Many Requests’ Error From The Server?
• Rate Limiting with NGINX and NGINX Plus

Hello, I have the same problem. However, the difference here is when I want to login to my account. I found the message "429"
Whoops! Too many requests. Please try again later."

I previously created 1 server for my website, and I restarted it. Then I logged out of my account and I tried to run it again by first logging into my account.