Servers
The server workspace
The thirteen tabs, what each is for, and which one to open for a given problem.
Click a server's name on the Servers page and it opens with thirteen tabs down the side. On a phone they become a strip you can scroll sideways.
Opening a server creates a live connection to it. That connection closes by itself after 30 idle minutes; come back and it reconnects.
The thirteen tabs
| Tab | One line |
|---|---|
| Monitor (opens first) | Live CPU, memory, disks, network, and what is using them |
| Services | Everything that should be running, with start / stop / restart |
| Logs | Read what the server wrote when something happened |
| File manager | Browse, edit, upload, download, zip |
| Terminal | A real command line, with an AI helper beside it |
| Docker | Containers, images, volumes, networks, compose |
| PM2 | Node.js apps kept running by PM2 |
| Nginx | Web server: sites, config, test, reload, errors |
| Packages | Updates, security fixes, reboot |
| Users | Who can log in, and with what |
| Scheduled | Jobs that run on a timetable |
| Disk usage | What is filling the disk, folder by folder — and delete it |
| Activity | The permanent record of what was done |
Which tab do I want?
| The problem | Start at |
|---|---|
| "My website is down" | Services → is it running? Then Logs → why did it stop? |
| "The site is slow" | Monitor → CPU, memory, load, top processes |
| "Disk is full" | Disk usage → scan and find the biggest folders; then Docker (unused images) if it's Docker's storage |
| "I need to change a setting" | File manager, or Nginx for web config |
| "Is my server missing security fixes?" | Packages |
| "Who has access to this machine?" | Users |
| "What runs at 3 am?" | Scheduled |
| "Did someone change something?" | Activity |
| "I don't know where to start" | Ask the AI assistant |
Most warnings on the health card are clickable and land you on the right tab, with the right item already selected.
Things worth knowing
Tabs stay open. Switching tabs — or even navigating away in the sidebar and coming back — does not restart anything. A running terminal, a log you are following and a streaming chat all survive.
Everything runs as the login you configured. If that login is not root
and has no sudo rights, some buttons will fail with a permissions error. That
is the server refusing, not a bug here. The
readiness check in guided tasks warns about this
before you start.
Everything is recorded. Every action on every tab is written to the Activity log with your name, the time, and whether it worked. Passwords and tokens are masked.
Viewers get a reduced set. A Viewer can open Monitor, Logs, Services, Docker, PM2, Nginx, Packages, Scheduled, Users and Activity read-only, and cannot open the Terminal or the File manager at all. They see the message "Your role can look at this server but not change it." See Roles.