Managing your server

Everything that happens after your server is running: powering it on and off, changing its size, reinstalling it from scratch, reaching its screen directly, and deleting it.

Click a server in the Servers list and you will see a summary strip at the top (vCPU, RAM, disk, hourly and monthly price) with tabs below it.

OverviewLocation, image, IP, server ID and recent actions.
GraphsCPU, disk and network usage; live or historical.
NetworkIPv4 address and rDNS record.
PowerStart, stop, reboot, reset.
ResizeChange the server type.
RebuildReinstall from an image.
FirewallsRules applied to this server.
DeleteRemove the server permanently.

Power actions

The switch on the Power tab turns the server on and off. The buttons next to it restart it.

ActionWhat it doesWhen to use it
StartPowers on a stopped serverTo bring back a server you stopped or that was suspended
StopSignals the OS to shut down, forces it if there is no responseWhen you will not use the server for a while
RebootShuts down cleanly and starts againKernel updates, configuration changes
Reset (hard)Restarts the machine without waiting for a signalWhen the server is completely frozen and neither SSH nor the console responds

Stopping does not stop the charges

A stopped server still reserves disk, IP and capacity, so it is still billed. Deleting is the only action that stops charges. If you no longer need a server, don't stop it — delete it.

Stopping asks for confirmation, because unsaved data can be lost if something is still running. Shutting down sensitive services such as databases from inside the server first is a good habit.

Treat a hard reset as a last resort

A reset is the same as pressing the reset button on a physical machine: a disk write can be cut off halfway and the file system can be damaged. Try a reboot first, and if that doesn't help, look at the console.

Console

The Console button opens the server's screen in your browser. It is not the same as SSH: it connects through the virtualisation layer rather than over the network. That means it still works when you have broken the network configuration, locked yourself out with a firewall rule, or the server cannot reach the network at all.

1
  • The server must be running — a stopped server has no screen.
  • 2
  • Press Console; the server's screen opens in a new tab.
  • 3
  • Log in. SSH keys do not apply on the console; you need a username and the root password.
  • If you have no root password

    If you created the server with an SSH key only, there is no root password, so you cannot log in on the console. To keep the console usable as a recovery path, set a root password when creating the server, or set one while you are connected over SSH.

    If your browser blocks the new tab, the panel shows you a link to click. The console address is single-use and expires quickly; don't share it, just open it again when you need it.

    Changing the server type

    The Resize tab moves the server to a more powerful (or more economical) type.

    1
  • Stop the server — a running server cannot be resized.
  • 2
  • Pick the new type; the card shows its hourly and monthly price.
  • 3
  • Press Resize, then start the server when the action completes.
  • The new price applies from the next hour, and the monthly cap becomes the new type's cap. Only one resize runs at a time; a second one is rejected while the first is in progress.

    If the action fails, your type does not change

    The new type is not written to your server until the infrastructure has actually applied it. If something goes wrong the server stays on its old type and billing continues on the old type — you never pay for hardware that wasn't delivered.

    Watch the disk when moving to a smaller type: if the new type's disk is smaller than your data, the infrastructure rejects the change and your server keeps running on its current type.

    Rebuilding

    Rebuild reinstalls the server from scratch. Its name, ID and IP address are kept; everything on the disk is erased.

    Choose the same image and the server returns to a clean state. Choose a different image and the operating system changes — you don't need a new server to move from Ubuntu to Debian.

    This cannot be undone

    Back up your data somewhere else before rebuilding. You are asked to type the server's name to confirm; that is there to stop you from wiping the wrong server.

    Your SSH keys are applied again exactly as they were on first install, so you can connect with the same key as soon as the rebuild finishes.

    Graphs

    The Graphs tab shows CPU, disk and network usage. The selector at the top right switches between Live (last 30 minutes, refreshed every few seconds), 1 hour, 12 hours, 24 hours, 1 week and 30 days.

    The CPU graph is scaled to the core count: one fully used vCPU reads 100%.

    Deleting a server

    The Delete tab removes the server and its disk permanently. You must type the server's name to confirm.

    Deleting is the only action that stops both the server and the IPv4 charges. A deleted server cannot be brought back; its disk, snapshots and data cannot be recovered.

    Before you delete

    Download your data, point your DNS records at another server, and review any firewall rules that were attached to it.