Console and servers
Server lifecycle, web console access, SSH keys, teams and cloud-init.
Servers
The console lists every server in your team, with its region, plan, IP addresses and current state. Click a server to open its detail view.
| Action | What it does |
|---|---|
| Power on / off | Hard power control. Prefer a graceful shutdown from inside the OS. |
| Reboot | Sends an ACPI reboot, then forces it if the machine does not come back. |
| Rebuild | Reinstalls the OS from an image. The disk is wiped, so take a snapshot first. |
| Resize | Changes vCPU and RAM. Disk can grow but not shrink. Reboot required. |
| Snapshot | Captures the whole disk. Runs online; no downtime. |
| Destroy | Deletes the server and its disk. Snapshots survive retention. |
Console access
If SSH is unavailable, open the web console from the server page. It connects to the serial console, so it works even when networking is misconfigured. Copying and pasting is supported; file transfer is not.
SSH keys
Add keys under Account → SSH keys and select them when creating a server. Keys are injected through cloud-init on first boot. You can add a key to a running server by appending it to ~/.ssh/authorized_keys yourself, or rebuild from an image with the new key selected.
Teams and roles
Every account has a team. Invite members with one of three roles:
- Owner — billing, members and all resources.
- Member — create and manage servers, DNS and snapshots.
- Read-only — view resources and logs, no changes.
Role changes take effect immediately. Removing a member revokes their API tokens.
Images and cloud-init
Choose a public image or upload your own. On first boot, cloud-init applies your SSH keys, hostname and an optional user-data script. A minimal user-data example:
#cloud-config
packages:
- nginx
- fail2ban
runcmd:
- systemctl enable --now nginx
Common problems
- Permission denied (publickey) — confirm the key was selected at create time and that you are using the matching private key.
- Server unreachable — check the cloud firewall and the OS firewall. Use the web console to confirm the machine booted.
- Resize stuck — the machine must be off. Power it off, wait for the state to settle, then resize.
