Create, Configure and Deploy VPN server
Learn how to configure and deploy a VPN server with all your assets on BugBase
Pre-requisites
Have a Company Account on BugBase
Creating & Configuring a VPN Server
To create and configure a VPN server:
Login to your company dashboard.
Navigate to the Assets Page via the sidebar, then choose the VPN tab.
Click on "Create VPN."

VPN Dashboard Configure your VPN server by adding the following details:
Server name: Assign a descriptive name to your VPN server.
Set rate limit: Establish a rate limit for your VPN server to ensure optimal performance and prevent overuse. Add the rate limit in requests per minute. This helps in managing the server load effectively and ensures a stable connection for all authorised users.
VPN Server Location: Select the countries from which you would like your bug hunters to have access.
Domains: Choose all your sensitive domains. You can include an active time range for testing this domain and also add blacklist routes.

Create VPN server Adding domains to VPN server
( You can add multiple targets to a VPN server )
Select an asset, or enter a custom URL: For each target you can either pick one of your company assets from the dropdown, or type a custom URL / host / IP in the "Or whitelist a custom URL" field. A custom target can be a bare host (
app.example.com), an IP (10.0.0.5), or ahost:port(app.example.com:8443) — paths and non‑standard ports are supported. Tip: Only the host (and port) is used for whitelisting — the VPN routes traffic to that host, so a full URL likehttps://portal.example.com:444/appis accepted and reduced toportal.example.com:444. Click here to learn how to add assets.Active Time Range: Specify an active time range when you want the bug hunters to access the target on a daily basis. The hours selected will default to the UTC timezone.
Add Blacklist Routes: You can blacklist API routes that you do not want bug hunters to access, even through the VPN.

Add Assets to VPN
Once you have added all the details, click on "Create VPN Server" to create the server.
Deploying the VPN server
Click on "Deploy Server" to deploy the server. NOTE: Deployment might take 1-2 minutes. DO NOT CLOSE THE PAGE.
Once the server status changes to "running," your VPN server is ready for use.

Whitelist the VPN's public IP
If your targets sit behind a firewall or IP allow‑list, allow the VPN server's public IP so traffic from bug hunters (which egresses through the VPN) can reach them.
On the VPN page, copy the IP Address shown for the server — this is the VPN's public IP.
Add that IP to your target's firewall / WAF allow‑list.
Test the VPN yourself (sanity check)
Before exposing the VPN to bug hunters, you can generate your own connection profile to verify it works end‑to‑end.
On a running VPN server, click "Download My Config".
Import the downloaded
.ovpnfile into any OpenVPN client and connect.Confirm you can reach your whitelisted target(s) while connected — and that other destinations are blocked.
Make the VPN visible to bug hunters
VPN servers are hidden from bug hunters by default. When you're satisfied with the configuration, expose it using the "Visible to researchers" toggle on the VPN page.
Off (default): No bug hunter can see, download, or use the VPN — even on programs whose in‑scope assets it covers.
On: Bug hunters who are accepted members of your program (and not blacklisted) can download the config and connect.
Updating the configuration
To update the configuration of the VPN server, simply update the values and click on "Re-deploy Server".

Stopping the server
When your server status is "running," click on the "Stop Server" button to stop the server.

Last updated