Tunnels

Install the CLI

On macOS and Linux, run the installer. It puts rimbra in /usr/local/bin, or ~/.local/bin when that isn’t writable. On Windows, download rimbra-windows-amd64.exe from the link below and run it from a terminal.

curl -fsSL https://rimbra.app/install.sh | sh
rimbra version

Sign in with a tunnel token

1. Open Tunnels in the dashboard sidebar and choose New token. Give it the name of the computer it’s for.
2. Copy the token. It’s shown only once; Rimbra keeps only a hash of it.
3. Run rimbra login and paste it. It’s saved in ~/.config/rimbra/config.json, readable only by you.

Start a tunnel

Give the port your app listens on. The address prints at once and each request is listed as it arrives. Press Ctrl+C to stop.

rimbra tunnel 3000

  https://tunnel-8f2c1a9e.rimbra.live  →  http://localhost:3000

  10:42:07  GET    /            200  14ms
  10:42:08  POST   /api/hook    204  3ms

Options

What your app receives

• Every method, header and body, with request bodies up to 32 MB.
• Streamed responses and server-sent events, as your app writes them.
• Websockets, including the hot reload of most dev servers.
• X-Forwarded-For with the visitor’s IP, X-Forwarded-Host with the public address and X-Forwarded-Proto: https.
• Your app has 60 seconds to start answering. After that the visitor gets a 504.

Price and limits

Tunnels is a $4/month add-on on any plan: 1 tunnel with its own subdomain and 5 GB transfer a month, then $0.20 per GB from your points. The $10/month Developer pack includes Functions, Queues, Tunnels and Buckets with double the allowances. Without the add-on the Tunnels page asks you to pay first, and new tokens can’t be made.

Transfer counts what goes through a tunnel in both directions and resets each billing cycle. Past it, pay as you go pays from your points; with it off, or with no points left, tunnels stop carrying requests until the next cycle.

Without the add-on the CLI is refused with 402 plan_required until you add Tunnels. Tokens are kept, so the same ones work again.

A tunnel with no requests for 4 hours closes on its own. A tunnel never takes the address of a live app: if a name is already an app’s, pick another.

See and stop tunnels

The Tunnels page charts requests through your tunnels by status over the last 24 hours or 7 days (30 days on paid plans), lists every connected tunnel with its address, local port, start time and request count, and shows the latest 50 requests across them. Open a tunnel to see only its requests. Stop ends a tunnel and tells the CLI not to reconnect. Tokens live on their own tab; revoking a token closes every tunnel using it.

Messages from the CLI