Servers
Managing a running server
What the server page lets you do: reboot, rename, extend the term, switch auto-renewal, resume a suspended server, cancel, and what each action costs.
Everything about a running server lives on its page in the console. Actions that cost money say so before they run, and destructive ones ask twice.
| Action | What it does | Cost |
|---|---|---|
| Reboot | Hard reset through IPMI. Back in under two minutes; NVMe data untouched. | none |
| Rename | Changes the label in the console and the API. The hostname does not change. | none |
| Extend | Charges one more term now and pushes the renewal date out by one term. | one term |
| Auto-renew on / off | Off: the server stops at the end of the paid term and is erased 14 days later. On again before that: nothing lost. | none |
| Resume | Brings a suspended server back exactly as it was. | one term |
| Re-image | Reinstalls the chosen OS and template. Wipes the NVMe. Same price, same address. | none |
| Cancel | Immediate. The server is released and erased; the rest of the paid term is not refunded. | none |
Statuses
- provisioning
- Ordered, being installed. Address shown when ready.
- online
- Running, paid until the date shown.
- renewal due
- The term ended and the balance did not cover it; 72 hours of grace, still online.
- suspended
- Powered off, data kept 14 days. Resume charges one term.
- cancelled
- Released and erased. Kept in the list for your records.
From the API
GET /api/v1/servers returns the same statuses and dates. Actions are not exposed yet; they follow feature by feature, and the reference says which are live.