Tunneling

Mo runs in a hosted browser. Use a tunnel when the app you want to test is on your machine or a private network. You can start one with the qa CLI or run the Connector Docker image on a network host.

Tunneling is in alpha. Behavior may change, and performance is not guaranteed.

Prerequisites

Allow outbound TCP 443 from the machine running qa tunnel or the Connector container to these IP addresses. Tunnels currently connect through West US 3.

Destination	IP address
Shared API	`34.149.80.75`
West US 3	`135.234.111.33`

The machine also needs DNS resolution and network access to the target app.

Tunnel with the CLI

Use qa tunnel when the app is reachable from the machine running the CLI. Start the tunnel for the exact address Mo will open, then pass its ID to qa start:

tunnel_id=$(qa tunnel start localhost:3000 | jq -r .tunnelId)
qa start "Test the checkout flow on http://localhost:3000" --tunnel "$tunnel_id"

The address can also be a private hostname or IP address. For example, if your machine can reach staging.internal:8080, you can tunnel it without Docker:

tunnel_id=$(qa tunnel start staging.internal:8080 | jq -r .tunnelId)
qa start "Test the checkout flow on http://staging.internal:8080" --tunnel "$tunnel_id"

Keep the tunnel running until the session finishes, then stop it with qa tunnel stop "$tunnel_id". Pass more addresses to qa tunnel start if the flow needs them. The qa tunnel reference covers foreground mode and listing tunnels.

Run the Connector with Docker

For a VM that can reach an internal app, run the Connector container there. The Connector needs outbound access to Momentic and does not open an inbound port on your network. Get the Connector image from Momentic before starting.

Start the Connector

Set CONNECTOR_IMAGE to the image reference Momentic gave you, and set MOMENTIC_API_KEY to your organization’s API key. This example lets Mo open https://app.internal.example through a Connector named internal-poc:

export CONNECTOR_IMAGE='<image supplied by Momentic>'
export MOMENTIC_API_KEY='<Momentic API key>'
export MOMENTIC_APPROVED_APPS='[{"name":"internal app","browserAddress":"app.internal.example:443","target":"app.internal.example:443","scheme":"https"}]'

docker run --detach \
  --name momentic-connector \
  --network host \
  --volume momentic-connector-state:/var/lib/browser-fleet-connector \
  --env MOMENTIC_API_BASE_URL=https://api.momentic.ai \
  --env MOMENTIC_API_KEY \
  --env MOMENTIC_CONNECTOR_NAME=internal-poc \
  --env MOMENTIC_APPROVED_APPS \
  "$CONNECTOR_IMAGE"

browserAddress is the host and port Mo opens. target is the host and port the Connector reaches on your network. Set scheme to http or https to match the app. On a Linux host, --network host lets the Connector reach services bound to the host’s loopback address. Keep the state volume so the Connector retains its identity across restarts. Check docker logs momentic-connector to confirm enrollment succeeds. Then start a Mo session with the Connector name:

qa start "Test the sign-in flow on https://app.internal.example" --tunnel internal-poc

See use the Mo CLI for installation and sign-in.

Get started

Essential guidelines

Set up Mo

Working with Mo

Prerequisites

Tunnel with the CLI

Run the Connector with Docker

Start the Connector

​Prerequisites

​Tunnel with the CLI

​Run the Connector with Docker

​Start the Connector

Prerequisites

Tunnel with the CLI

Run the Connector with Docker

Start the Connector