Skip to main content
The server management dashboard is your central hub for controlling and monitoring your game server. It provides real-time statistics, console access, and quick actions to manage your server effectively.

Server Dashboard

When you access a server, you’ll see the main dashboard which includes:
  • Server Console - Real-time console output and command input
  • Power Controls - Start, stop, restart, and kill buttons
  • Resource Statistics - CPU, memory, disk, and network usage graphs
  • Server Details - Quick overview of server status and allocations

Server States

Servers can be in various states that affect available actions:
StateDescriptionActions Available
runningServer is online and operationalFull access
offlineServer is stoppedStart only
startingServer is booting upLimited
stoppingServer is shutting downLimited
installingInitial installation in progressNone
suspendedServer has been suspendedNone
restoring_backupBackup restoration in progressNone
When a server is installing, suspended, or under node maintenance, most actions will be unavailable.

Server Information

The server overview displays key information:
Server Object
{
  "uuid": "7e8e8f18-25fa-4f9e-a13d-4d1c8e8b8f9e",
  "name": "My Minecraft Server",
  "description": "A survival server for friends",
  "status": null,
  "node": "Node 01",
  "limits": {
    "memory": 4096,
    "disk": 10240,
    "cpu": 200,
    "swap": 512,
    "io": 500
  },
  "feature_limits": {
    "databases": 2,
    "allocations": 5,
    "backups": 3
  }
}

Resource Utilization

The dashboard displays real-time resource usage through the Wings daemon:
1

CPU Usage

Shows current CPU percentage and historical data. The limit is based on your allocated CPU cores (e.g., 200% = 2 cores).
2

Memory Usage

Displays RAM consumption in MB/GB with a graph showing trends over time.
3

Disk Usage

Shows total disk space used by server files, including backups stored locally.
4

Network I/O

Real-time network traffic in/out measured in KB/s or MB/s.

API Endpoint

Resource statistics are fetched via WebSocket connection:
GET /api/client/servers/{server}/websocket
Response
{
  "object": "websocket_credentials",
  "attributes": {
    "token": "eyJ0eXAiOiJKV1QiLCJhbGc...",
    "socket": "wss://node.example.com:8080/api/servers/{uuid}/ws"
  }
}

Server Permissions

Users and subusers can have different permissions:
  • Server Owner - Full access to all features
  • Subusers - Custom permissions set by owner

Common Permissions

  • control.console - Access console and send commands
  • control.start, control.stop, control.restart - Power actions
  • file.* - File management permissions
  • database.* - Database management
  • schedule.* - Task scheduling
  • backup.* - Backup operations
  • allocation.* - Network allocation management
  • startup.* - Startup parameter modification
  • settings.* - Server settings changes
Permissions are checked both in the panel UI and at the API level. The server owner always has all permissions.

Activity Logging

All server actions are logged to the activity log, which can be viewed from the dashboard:
GET /api/client/servers/{server}/activity
Activities include:
  • Power state changes
  • File operations (create, edit, delete)
  • Database modifications
  • Backup creation/restoration
  • Schedule execution
  • Settings changes
Each log entry includes:
  • Timestamp
  • User who performed the action
  • Action type (e.g., server:console.command)
  • Additional properties/metadata

Installation Status

During initial server creation or reinstallation, you’ll see installation progress:
GET /api/client/servers/{server}
Servers cannot be used until installed_at is set and status is not installing or install_failed.

Next Steps

Console

Send commands and view live output

File Manager

Manage server files and configurations

Databases

Create and manage MySQL databases

Schedules

Automate tasks with cron schedules

Backups

Backup and restore your server

Network

Manage port allocations

Build docs developers (and LLMs) love