Skip to content

Check and maintain a server

Open Servers and press a server’s name. Its page shows its facts (OS, CPUs, memory, disk and what is in use), the running containers, and the Actions card.

A viewer can look. Testing needs a developer. Preparing and changing a server needs an admin or the owner.

Press Test connection. The platform logs in, remembers the server’s host key on first contact, and reads the basics: OS, CPUs, memory, disk and what is in use.

Press Check readiness. The platform asks the server every readiness question and stores the answers with a verdict: passed, warnings, failed. Nothing is changed on the server. Earlier runs stay listed under Earlier runs.

Press Prepare and confirm. It installs Docker, the firewall, the proxy and monitoring, then runs the readiness checks. It takes a few minutes. Running it again is harmless: each step skips what is already done.

In the Run a command card, type one shell command (for example docker ps), choose a Time limit, and run it. The output is shown on the page, and the command is written to the audit log.

Old images pile up after many deploys.

  1. In Actions, start Docker cleanup.
  2. Read the preview: the unused images it would remove.
  3. Confirm. If nothing is unused, it says so and removes nothing.

The server’s metrics show CPU, memory, disk, load and network, live or over 1 hour, 24 hours, 7 days or 30 days. See Monitoring.

Only do this if the server was reinstalled. The next connection test then accepts whatever key the server shows and remembers that one.

Press Remove server and confirm. A server that still has environments is not removed: delete those first.