Skip to content

Testing private sites with remote browsers

A remote browser can only test what it can reach. Your app on localhost:3000, a LAN address, or an internal VPN doesn’t exist from a browser running in a cloud — so every remote-browser setup needs an answer to: how does the browser see the app?

The right answer depends on which kind of remote browser you have, because the capabilities differ:

Your browser runs onYou control the machine?Best answer
A cloud computer you rentedYes — rootJoin it to your VPN (Tailscale)
A managed cloud browserNoThe vendor’s tunnel product
Either, occasionally—SSH reverse tunnel / public staging

Cloud computers: join the box to your tailnet

Section titled “Cloud computers: join the box to your tailnet”

If you run the browser on a machine you control (cloud computers), the clean solution is a VPN between the box and wherever the app lives. With Tailscale:

Terminal window
# on the browser box (root, one time)
curl -fsSL https://tailscale.com/install.sh | sh
tailscale up

The box is now on your tailnet, and the browser on it can reach the app by MagicDNS name — no per-test tunnels, no exposing anything publicly:

Terminal window
vibium start http://127.0.0.1:9515 # protocol, as usual
vibium go http://dev-laptop.tailnet-name.ts.net:3000

Two connections, two jobs: the SSH tunnel (or fly proxy) carries the protocol from vibium to chromedriver, and the tailnet carries the page traffic from the browser to your app. They’re independent — though once the box is on the tailnet you can also run the SSH tunnel over it (ssh -L 9515:127.0.0.1:9515 root@browser-box.tailnet-name.ts.net) and drop the box’s public SSH exposure entirely.

Plain WireGuard works identically if you’d rather not use Tailscale; you’re just doing the key exchange and routing yourself.

Managed cloud browsers: the vendor’s tunnel

Section titled “Managed cloud browsers: the vendor’s tunnel”

You can’t install anything on a managed vendor’s browser host, so the grids ship page-traffic tunnels that solve reachability from their side: BrowserStack Local, Sauce Connect, the LambdaTest tunnel, TestingBot Tunnel. Each is a small binary you run next to the app; the vendor’s browser routes matching traffic back through it. They change nothing about how vibium connects — protocol and page traffic stay separate — and each grid’s guide covers its tunnel flag once the guides are verified.

Vendors without a tunnel product may still support customer-supplied proxies — Kernel does: an authenticated HTTP/HTTPS proxy you run at your network’s edge, bound to the browser at create time (proxy_id), routes its page traffic into your infrastructure. Unlike the grids’ tunnels, your proxy must be reachable from the vendor’s side — an internet-facing, authenticated surface (Tailscale Funnel in front of a proxy on your tailnet is one way to build it). Failing that, the fallback is making the app itself reachable: a deploy preview or a staging URL behind auth.

For a one-off against a box you control, plain SSH does it without any VPN: ssh -R 3000:localhost:3000 user@browser-box makes your laptop’s app appear at localhost:3000 on the box, and the browser there can vibium go http://localhost:3000. Symmetric with the -L tunnel the recipes already use for the protocol.

The cloud bench defaults to a public target because it compares vendors, and a target must be reachable from every browser’s location. Benching a private app only works for browsers that can reach it — tailnet-joined cloud computers, not managed vendors — so cross-vendor numbers against a private target aren’t comparable. Set BENCH_URL for a house default target.