Server detail sections

1. Monitoring

The landing section, and where to start when something is wrong.

Resource graphs — CPU, memory, disk and network over a selectable window.

Bandwidth and Monthly Usage — transfer consumed, against the plan's allowance. Worth watching: bandwidth over the allowance is billed separately.

Service Health

System Reports — collected diagnostics for the server.

Notifications & Alerts — what has been raised recently, tied to the thresholds set in Health Alerts.

Each panel shows Updated at, so you know how fresh the reading is.

2. Packages and Services

Everything installed, and control over it.

Packages — the installed list with Current Version against Latest, so you can see what is behind. Install Package adds one.

Extensions / PHP Extensions — enable and disable extensions per version.

PHP Configuration — edit PHP settings from the panel rather than by hand.

Nginx Configuration — the web server's configuration, with Priority controlling the order rules are applied.

Additional Details — version and build information per package.

Logs — pick a Log source and fetch it. Use this when a service starts and immediately stops; the reason is almost always here.

3. Caching

Cache services (Redis, Memcached and similar), each with:

Overview — installed state, version, running or not.

Connection Information — host, port and credentials for connecting from your application.

General — basic service settings.

Memory Management — the limit and the eviction policy: what is discarded when the cache fills. This is the setting that decides whether a full cache slows down or starts refusing writes.

Network — bind address and port.

Persistence — whether cached data survives a restart.

Live Configuration on Server — what the service is actually running, read from the machine, not what was last saved. When the two differ, that difference is the thing to investigate.

Logs — choose a Log source and Fetch Logs.

4. Other Services

Services beyond the core stack.

Add Custom Package — install something the catalogue does not carry.

Custom Command Script — an App Name and the Command to run, for services that need a bespoke start-up.

Configured VHosts — virtual hosts defined on the server.

Connection Information — how to reach each service.

Installation Failed — shown when an install did not complete; the log is attached to it.

Logs — same Log source and Fetch Logs controls as elsewhere.

5. Scaling

Change the server's size.

Current Plan — vCPU, Memory, storage, Bandwidth, and the Server Price you pay now.

Option Selection — the plans you can move to, with the new price. Scaling resizes the underlying VPS: the provider usually requires a reboot, and billing changes from that point.

Scaling up is generally straightforward. Scaling down is often restricted by the provider once disk has been allocated — check before you rely on it.

6. Volumes

Storage attached to the server.

Included Root Storage — the disk that came with the plan, marked Bundled with droplet plan.

Attached Volume Storage — additional High-speed Block Storage volumes, billed separately from the server.

Mount Storage Volume — attach a volume with:

Delete Storage Volume — destroys the volume and everything on it.

No Storage Volumes Attached is the empty state. Add a volume when data outgrows the plan's disk rather than scaling the whole server.

7. Access

Who can reach this server.

Panel users and team members with access, and their per-server permissions — this is what produces Access Restricted in sections a team member may not use.

Also lists authorised SSH keys, with Delete SSH Key.

Connection Error appears when the panel cannot reach the server, which is usually the firewall or a machine that is powered off.

8. SSH Key

Root SSH access.

Key Name and Public Key — add a key rather than editing authorized_keys by hand, so the panel's view stays accurate.

Select Option chooses how the key is applied.

Granting root access changes the server's manageability state, and the panel can no longer guarantee its configuration. Deliberate, and visible on the server card afterwards.

9. Firewall

Inbound and outbound rules. Anything not opened is closed.

Inbound rules and Outbound rules, each rule carrying:

Filter by narrows a long rule list.

The Security Note on the page is worth heeding: the most common avoidable exposure is a database port open to 0.0.0.0/0. Open ports to your application server's address, not to the world.

10. Backup

The largest section, covering three different things.

Server backups

Scheduled backups of the whole server, with Backup Name, Created At, and per-backup actions. Auto Delete On shows when a backup ages out of retention.

Images

Create Image takes a server image — a full snapshot you can build new servers from.

Auto-Image Schedule automates it: frequency, time, and (for weekly) a day. The header shows when the next image will be taken. Confirm Schedule summarises frequency, time, day and timezone before saving.

Portable backups

Auto-Portable Backup Schedule produces backups in a portable format, for moving a server elsewhere rather than restoring in place.

Clone Server

Clone Server copies this server to a new one. Advanced vCPU Options lets the clone take a different size, and Confirm Clone shows what will be created and what it will cost before you commit.

11. Applications

The applications on this server. Each has its own page.

App Name, and an Edit Application Icon control for the list.

Source — the same options as server creation: Deploy from Git Repo with Branch to Deploy, Authentication (token or deploy key), or a container with a Container Port.

Database — the database bound to the application, with its credentials.

Deployment Script — commands run on each deploy (build steps, migrations, cache warming).

Create Staging Environment — a copy of the application to test against before touching production.

Clone Application — duplicate it, on this server or another.

Delete Application — removes it and its data.

An application's own page carries its domains, SSL, backups and restore, and a database manager.

12. Database

Databases on this server.

Import Database and Export Database move data in and out. Restart restarts the database service.

Select provider chooses the engine when more than one is installed. No Database Provider Installed means no engine is present — install one from Packages and Services.

13. Cronjob

Scheduled tasks: the command, the schedule, and whether the last run succeeded. Failures also surface under Cron Job Failures in Monitoring.

14. Domains

Domains pointed at this server.

Watch Expiry Date — an expired certificate takes a working site offline as completely as a crashed server, and looks worse to visitors.

15. Containers

For Docker hosts.

Containers with their state, logs and lifecycle, plus:

Application URL and Access Type — how the container is reached.

ADD DOMAIN with an A record to point at it.

Auto-Backup Schedule, Backup Now and Backups — container backups on the same footing as application backups.

Assign Docker Client / Assign Client — attach a container to a client for multi-tenant setups.

16. Supabase

For servers running the Supabase stack.

Details — Current version against Latest version, so you can see when an upgrade is available.

Containers — the services making up the stack.

Database and DB Connections — the Postgres behind it and what is connected.

Buckets — storage buckets.

API Endpoints — the URLs your application calls.

Current access — who can reach it.

Installation log — what happened during setup, and the first place to look if something did not come up.

Danger Zone → Complete Removal — removes Supabase and its data from the server.

17. Infracaptain

For servers running Infracaptain.

Infracaptain Dashboard link, Server ID, and Status.

18. Health Alerts

Thresholds that raise an alert — CPU, memory, disk — and where notifications go. What fires here appears under Notifications & Alerts in Monitoring.

Set a disk threshold on every server. A full disk fails in ways that look like unrelated problems: uploads break, logs stop, databases refuse writes, and nothing says "no space" until you look.

Quick reference