Can I get Loadster’s IP addresses for my whitelist?
Loadster spins up on demand cloud instances to run your load test, so we normally won’t know the IP addresses ahead of time. Most of our customers actually prefer this since it’s best to simulate load from many different locations at once (for a more realistically distributed test), and it allows them to properly exercise load balancers that do round robin IP-based load balancing.
However, if your situation requires that you know Loadster’s IP addresses ahead of time, we might have a solution for you.
When is IP whitelisting necessary?
If you’re testing a private application behind a firewall, you may want to whitelist certain IP addresses to allow the Loadster traffic to reach the application.
Also, some load balancers and web application firewalls (including those made by Cloudflare and our friends at Nginx) have a DDoS protection feature that watches for a large flood of traffic from the same IP address, and blocks or throttles subsequent traffic from it.
What are some alternatives to IP whitelisting?
There are a few other things you might want to explore before going to the trouble of requesting fixed Loadster IPs and setting up a whitelist.
- Configure your load balancer or firewall to allow requests with a special header, and then add a
code block at the beginning of your script to set the header globally.
http.setGlobalHeader('X-Loadster', 'true')would set a header for Protocol Bots, or
browser.setGlobalHeader('X-Loadster', 'true')would set it for Browser Bots. When the bots run your script, all requests will include that header, so your firewall can allow the traffic.
- Disable the IP blocking feature on your application firewall temporarily. If it’s a production site, you might get some pushback from your team, but then again if you are load testing in production we’ll assume everyone is on the same page already!
- Host your own Loadster Engine on an IP (or multiple IPs) of your choosing, rather than the on demand Loadster Cloud regions. This may be the easiest option and you’ll have full control of the IPs and environments that way, but it might be prohibitively complicated from an operational standpoint if you are running a large load test that requires many engines.
What if I really need to run cloud tests from fixed IP addresses?
If none of the workarounds work for you, please contact email@example.com to discuss getting a special cluster set up just for you with a fixed IP address. Due to the additional costs and complexity imposed by our cloud providers, we can only configure fixed IPs for our paying customers at this time, and there might be some additional charges.