SSH Access
Every Rigbox workspace is a full Linux VM with SSH access. Connect from any terminal to get a shell or transfer files.Prerequisites
Before connecting via SSH, you need:- An SSH key pair on your local machine (e.g.,
~/.ssh/id_ed25519) - A Rigbox account with an API key
- At least one running workspace
Register an SSH Key
To connect via SSH, you first need to register your public key with Rigbox. Replace<KEY_NAME> with a label you’ll recognize (for example, laptop).
~/.ssh/id_ed25519.pub) and registers it automatically under the name you provide. To register a key from a different path, pass --file:
Sync Keys to a Workspace
When you create a workspace, your registered SSH keys are typically synced automatically. If you add a new key while a workspace is already running, sync it manually:~/.ssh/authorized_keys file.
Keys are synced automatically on workspace start for most templates. You only need to run
rig ssh sync if you add a key to an already-running workspace.Connect to a Workspace
When you create a workspace, Rigbox gives you an SSH command in this format:<WORKSPACE_ID_SUFFIX> is the workspace ID with the leading ws- stripped, and <REGION> is the workspace’s region (for example, eu-west-1).
For example, if your workspace is named my-project with ID ws-ctbxi8lb in the eu-west-1 region:
my-project / ws-ctbxi8lb / eu-west-1. Replace those with your own workspace name, ID suffix, and region.
The SSH server identifies you by your registered key and routes the connection directly to your workspace VM.
Connecting to the right region
Each workspace runs on a compute node in a specific region (today:eu-west-1), and you connect to that region’s hostname directly:
rig ssh-info <workspace> from the CLI prints the same target. As Rigbox expands to more regions, the hostname will change accordingly — there is no central rigbox.dev:22 gateway to fall back on.
Older
ssh <name>+rig@rigbox.dev instructions referred to a gateway router that is no longer deployed. If a third-party guide or older script still uses that format, replace it with the region-direct hostname.Specify an identity file
If your key is not in the default location, specify it explicitly:SSH config shortcut
Add this to your~/.ssh/config for easier access:
File Transfer
Usescp to transfer files between your local machine and a workspace.
Upload a file
Download a file
Upload a directory
Using rsync
For larger transfers or syncing directories,rsync is more efficient:
Managing SSH Keys
List your registered keys
List keys synced to a workspace
authorized_keys file.
Remove a key
Troubleshooting
Connection refused
If you getConnection refused, verify:
- Your workspace is running (check with
rig workspace ls) - Your SSH key is registered and synced
- You’re using the correct username format:
<WORKSPACE_NAME>-<WORKSPACE_ID_SUFFIX>@<REGION>.rigbox.dev
Permission denied
If you getPermission denied (publickey):
- Check that your key is registered:
rig ssh ls - Sync keys to the workspace:
rig ssh sync --workspace <WORKSPACE_ID> - Verify you are using the correct identity file:
ssh -v my-project-ctbxi8lb@{region}.rigbox.dev
Slow connection
If connections feel slow:- Check your network connection
- Try connecting with
-o ServerAliveInterval=60to prevent timeouts - For file transfers, prefer
rsyncoverscpfor large datasets
API Reference
- Add SSH Key - Register a new SSH key
- List SSH Keys - List registered SSH keys
- Delete SSH Key - Remove an SSH key
- Sync Workspace SSH Keys - Sync keys to a workspace
- List Workspace SSH Keys - List keys on a workspace