> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/troubleshooting/vpn-or-a-firewall.md).

# VPN or a Firewall

How to run BugBug cloud tests on an app behind a VPN or a firewall: allow the Cloud Proxy IP address, use a secret header or user agent, publish the app with ngrok, or run tests locally.

If your app [environment](https://docs.bugbug.io/editing-tests/variables.md#work-with-different-development-environments) 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](https://docs.bugbug.io/running-tests/in-cloud-on-server.md) because BugBug will not be able to access your app. You have several potential workarounds though.

{% hint style="warning" %}
Recommended solution:\
\
Set your VPN/Firewall/Server settings to allow the IP address of the Cloud Proxy selected in your project settings. See [Cloud runner IP addresses](https://docs.bugbug.io/preventing-failed-tests/project-settings.md#cloud-runner-ip-addresses).
{% endhint %}

{% hint style="info" %}
The current list of IP addresses is always available at <https://api.bugbug.io/v2/config/ips/>. If you automate your allowlist, read the addresses from this API response rather than hardcoding them.
{% endhint %}

## **Other options:**

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

Use a tool such as [ngrok.com](https://ngrok.com/) and publish your app publicly at the specific password-protected subdomain with authentication. More about ngrok? See [our documentation](https://docs.bugbug.io/running-tests/test-your-local-build-or-protected-web-page-using-ngrok.md) 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 browser settings of your [project settings](https://docs.bugbug.io/preventing-failed-tests/project-settings.md), set a shared secret value in **HTTP request headers** or **User agent**
2. In your VPN/Firewall/Server settings add a rule to allow traffic that contains this shared secret

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2F8YJettgG4aJVAXuR7L6d%2FZrzut%20ekranu%202023-03-17%20104152.png?alt=media&amp;token=5f613d89-5940-40ef-8234-9a16d2afc9d0" alt=""><figcaption></figcaption></figure>

### **Solution C: run tests locally**

You can still [execute the tests manually](https://docs.bugbug.io/running-tests/test-in-your-browser.md) on a machine that has access to the app environment. The disadvantage is that you can't [schedule tests](https://docs.bugbug.io/running-tests/schedules.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugbug.io/troubleshooting/vpn-or-a-firewall.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
