SSH and browser terminal

Browser terminal

In the dashboard, create or select a running container and choose Open terminal. It uses your browser session, a trusted Origin, and the selected container generation. API keys do not authenticate the browser WebSocket terminal.

The shell runs in the fixed tmux session main. Reloads and dropped connections can reattach while that generation is alive. Closing the panel detaches your client; the shell remains subject to idle and hard session deadlines.

SSH

Install cloudflared on your computer. Choose SSH in the dashboard, or request an access command through the API:

POST /containers/ssh
Authorization: Bearer mb_<your-key>
Content-Type: application/json

{"id":"<returned-id>","createdAt":"<returned-createdAt>"}

The response contains command, expiresAt (Unix milliseconds), and hostname. Run the returned command locally. Treat it as a credential: do not commit or share it.

Access goes through ssh.mainbrella.com to your running container. No public container IP or Mainbrella CLI is needed. Issuing a token does not start a container or renew idle time.

Session limits

Tokens last at most 15 minutes or until the hard container deadline, whichever comes first. Stopping or recreating a container invalidates its tokens. Each account permits ten live SSH tokens, and each container permits four combined browser/SSH terminal connections. Activity renews idle time, never the hard deadline.