Servers

Power, rename, rebuild and destroy servers, and set reverse DNS.

Each server’s page in the dashboard has its controls, network settings, snapshots, backups and activity. Everything here can also be done with the API using a token with the scope shown.

Statuses#

Status Meaning
Running On and reachable.
Stopped Off. You’re still billed for a stopped server, because its disk and IP addresses are kept for you.
Building, Setting up Being created or rebuilt.
Starting, Stopping, Rebooting A power action is in progress.
Rescue Booted into the rescue system.
Suspended Stopped for an unpaid invoice. It can’t be started until the invoice is paid. See Billing.
Error Something went wrong. Check the server’s activity, or contact support.

Operations#

Starting, stopping, rebooting, rebuilding and destroying a server are queued as operations. The request returns at once. The operation then runs, and only one runs at a time on a server: the next waits for the current one to finish. Each operation is queued, running, succeeded, failed or canceled, and the server’s Activity tab lists them, newest first.

From the API, these actions return 202 with the operation. Poll GET /servers/{id}/operations to follow it. A request that conflicts with what the server is doing returns 409.

Safe retries

Send an Idempotency-Key header with any value unique to the action, such as a UUID. If you send the same request again with the same key, you get the first operation back instead of queueing a second one.

Power#

Start, Stop and Reboot need servers:write. Stop and reboot ask the operating system to shut down cleanly. If it doesn’t respond, use Force stop or Force reboot, which cut the power like pulling the plug. Unsaved data can be lost.

curl -X POST "$API/servers/$SERVER/reboot" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"force": false}'

Power actions are refused while a server is suspended, being built or being destroyed.

Rename and deletion protection#

You can rename a server from its Settings tab. Names are unique within a workspace, ignoring case.

Turn on deletion protection for servers you can’t afford to lose. While it’s on, the server can’t be destroyed, from the dashboard or the API.

Reverse DNS#

Each IP address can have a reverse DNS (PTR) record, set on the server’s Network tab. Mail servers usually need one that matches the name they send as. Leave it empty to remove the record. Changes take a few minutes to show up.

Rebuild#

Rebuilding reinstalls the server from an image, with the SSH keys you choose. It keeps the server’s IP addresses, plan and backups, but erases its disk. Take a backup first if there’s anything you need.

A server with a snapshot in place can’t be rebuilt; commit or revert it first.

Destroy#

Destroying deletes the server and its disk and stops billing for it. It needs servers:destroy, which the Member role doesn’t have.

This can’t be undone

The disk is deleted and the server’s IP addresses are released. Backups of the server are kept, and still show on the Backups page until you delete them.