Skip to main content
You can SSH straight into any machine you own — plain ssh, scp, rsync, port-forwarding, and editor Remote-SSH all work.
The old ssh boxd.sh management shell (the boxd> REPL for creating and listing machines over SSH) has been retired. Manage machines with the boxd CLI instead — install it with curl -fsSL https://boxd.sh/downloads/install.sh | sh, then boxd auth login. Connecting into a machine over SSH still works, and is what this page covers.

​
The <vm>.boxd host alias

Each machine listens on a dedicated SSH port (in the 10000–30000 range) on the shared proxy IP. The boxd CLI writes a per-machine Host alias — <vm>.boxd, with the right HostName and Port — into your ~/.ssh/config, and keeps it in sync automatically on every boxd machine new / fork / list / remove / rename. There’s no separate command to run; install the CLI and the aliases appear.
The managed block is bracketed with # BEGIN boxd / # END boxd; nothing outside the markers is touched.

​
Direct SSH, SCP, port-forwarding, editors

Once the alias exists, everything standard works against <vm>.boxd:
You land as the boxd user with passwordless sudo. Working directory is /home/boxd.
Connecting to the bare myapp.boxd.sh hostname (port 22) reaches the proxy, not the machine — the management shell that used to live there is retired. Use the myapp.boxd alias (or boxd connect myapp) to get into the machine.
Direct SSH only works for the machine owner. Your SSH key must match the key registered to your account.

​
No CLI? Use boxd connect

If you can’t install the CLI on a given host but have it elsewhere, boxd connect <name> opens an interactive shell into the machine over the boxd API (no SSH config or host keys needed):

​
Adding more SSH keys

Sign in from a different machine with a new key and go through the browser link flow (boxd auth login). The new key gets linked to your existing account (matched by your identity).