Your laptop, reachable for a while
Some work needs a public address before it is ready to deploy: a payment provider calling your webhook, a teammate looking at a branch, your own phone opening the page. Rimbra Tunnels gives a server on your computer an HTTPS address on rimbra.live for as long as the command runs.
The CLI opens one outgoing connection to Rimbra, so there is nothing to open on your router or firewall. Each visit travels down that connection to the port you named and the answer comes back the same way.
Three commands
- 1
Install the CLI: curl -fsSL https://rimbra.app/install.sh | sh
- 2
Make a tunnel token under Tunnels in the dashboard, then run rimbra login and paste it.
- 3
Run rimbra tunnel 3000 with the port your app listens on. The address prints at once, and each request is listed as it arrives.
With the Tunnels add-on, rimbra tunnel 3000 --name api keeps the same address every time: api-<your workspace>.rimbra.live. Handy for webhook settings you only want to enter once.
Yours to switch off
- Tokens are shown once and stored only as a hash. Revoke one and its tunnels close at once.
- Add --auth user:pass and visitors sign in before anything reaches your machine.
- Stop any tunnel from the dashboard. Tunnels with no requests for 4 hours close on their own.
- A tunnel can never take the address of a live app.
- Request bodies up to 32 MB, and your server has 60 seconds to start answering.
Questions
Does it work with websockets and hot reload?
Yes. Websockets, server-sent events and streamed responses pass straight through.
What does my app see as the Host?
localhost:<port>, so dev servers that check the host accept it. The public address is in X-Forwarded-Host, or pass --host-header preserve to keep it as Host.
Is my laptop exposed to the internet?
Only the one port you name, only while the command runs, and only through the tunnel address. Nothing is opened on your network.