VPN or a Firewall

If your app environment is not publicly available, for example only available in your local network or a private network with a VPN or behind a firewall, you can't run the cloud tests because BugBug will not be able to access your app. You have several potential workarounds though.

Recommended solution: Set your VPN/Firewall/Server settings to allow BugBug to connect from our IP range. You can find the IP list here: BugBug IP list

We provide an IP list generated from the API in case of feature changes on our site. Please do not hardcode it to avoid future problems. Use API response. We are still developing for the better.

Other options:

Solution A: Publish your app but protect it with a password

Use a tool such as ngrok.com and publish your app publicly at the specific password-protected subdomain with authentication. More about ngrok? See our documentation on setting up this tool

Solution B: Add an exception in your firewall/VPN

Let in BugBug based on custom headers or custom user-agent.

1. In the project settings set your custom header to some shared secret value

2. In your VPN/Firewall/Server settings add a rule to allow traffic with headers containing this shared secret

Solution C: run tests locally

You can still execute the tests manually on a machine that has access to the app environment. The disadvantage is that you can't schedule tests.

Upcoming feature: we are working on a command line interface that would allow you to run BugBug tests remotely on your own internal development server.