Documentation
Everything you need to get around your box. Don’t have an account yet? 👉 Sign up first.
Logging in
ssh -p 2222 <user>@mbox.blue
You’ll land straight inside your own box as root (of your container — you
can’t touch anyone else’s). Your home directory is /root.
Persistence
Your box keeps running between logins. Disconnect whenever you like and SSH back in later — your files and any background processes are still there.
💡 To keep interactive programs running across disconnects, use tmux: start
it with tmux, detach with ^b d (CTRL + b, then d), and re-attach next
time with tmux attach.
Re-entering your box
Re-entering is just logging back in:
ssh -p 2222 <user>@mbox.blue
You can also be explicit:
ssh -p 2222 <user>@mbox.blue attach
Depending on your SSH client you may see the input device is not a TTY, in
which case pass -t to force a terminal:
ssh -t -p 2222 <user>@mbox.blue attach
Running one-off commands
You can run a command without opening an interactive shell:
ssh -p 2222 <user>@mbox.blue uptime
The command runs directly (no extra shell), so if you want pipes or redirection, wrap it yourself:
ssh -p 2222 <user>@mbox.blue sh -c 'ls -la | head'
Resetting your box
To get a fresh box (for example to pick up a newer image), destroy the current one and then log back in:
ssh -p 2222 <user>@mbox.blue destroy
ssh -p 2222 <user>@mbox.blue
Lifecycle commands
Special words you can pass when logging in to manage your box:
status— report whether your box is running.attach— (re)enter your box with a shell (the default when you log in).destroy— tear your box down; a fresh one is created on next login.
💡 Most commands can be shortened to their first letter, e.g. s for status.
A periodic reaper cleans up any stopped boxes every few minutes.
mbox.blue - Documentation