Web console

Every instance pod has a built-in browser terminal. No SSH client required.

When to use it

• You are on a network that blocks outbound SSH.
• You are on a borrowed machine and do not have your keys.
• You are debugging firewall rules and just locked yourself out.
• You just want to poke around quickly.

How to use it

1. Open your pod in the console.
2. Click the Shell button (it appears once the pod is Running).
3. A terminal slides open, already logged in as the pod's default user.

The console runs over a secure WebSocket on port 443, so it works on basically any network that allows HTTPS.

Instance pods only

The browser Shell is available on instance pods (Ubuntu and friends). Database pods do not get one - connect to those with a MySQL client using the connection details on the pod's page.

How it works (briefly)

When you click Shell, the console asks the API for a short-lived access ticket (POST /api/pods/:id/console-ticket). The ticket is valid for 30 seconds and works exactly once. The browser then opens a WebSocket to the pod with that ticket attached.

So even if someone snags a console URL, they cannot replay it.

Limitations

• It is a real shell, but it is meant for interactive use. Start long-running processes with tmux, screen, or a systemd service so they survive your tab closing.
• File uploads and downloads are not built into the console UI. Use scp, rsync, or an HTTP-based tool you install yourself.