Admin Getting Started
First User
When no users exist in the database, the registration page is accessible. The first user to register automatically becomes the admin.
Post-Setup Checklist
- Configure a node (add at least one node and install the daemon on the target machine)
- Add a location (create a location like "US East" for node organization)
- Add allocations (assign IP:port combinations to the node)
- Create or import an image (add a server image definition for the game servers you want to host)
- Configure settings (set panel title, enable features, configure rate limits)
- Enable registration (optional, turn on public registration if you want users to self-register)
Admin Panel Pages
| Page | URL | Description |
|---|---|---|
| Overview | /admin/overview |
Dashboard with stats and update checker |
| Servers | /admin/servers |
Manage servers |
| Users | /admin/users |
Manage users |
| Nodes | /admin/nodes |
Manage nodes and allocations |
| Databases | /admin/databases |
Manage database hosts |
| Images | /admin/images |
Manage server images |
| Locations | /admin/locations |
Manage geographic locations |
| Mounts | /admin/mounts |
Manage shared mounts |
| API Keys | /admin/apikeys |
Manage API keys |
| Addons | /admin/addons |
Manage addons |
| Settings | /admin/settings |
Panel configuration |
| Activity | /admin/activity |
Audit log |
| Player Stats | /admin/playerstats |
Player count history |
Key Admin Tasks
Adding a Node
- Go to Admin → Nodes
- Click "Create Node"
- Enter name, address, port, key, and resource limits
- Install the daemon on the target machine with the same key
- Verify the connection
Creating a Server
- Go to Admin → Servers
- Click "Create Server"
- Select owner, node, image, and allocate resources
- The server is created and queued for installation
Managing Users
- Create users with specific resource limits
- Assign roles for permission control
- Transfer server ownership when needed
- Reset onboarding state.
Security Recommendations
- Enable 2FA for all admin accounts (
require2faForAdmins: true) - Use a strong
SESSION_SECRET - Enable rate limiting
- Keep the panel updated
- Use HTTPS in production
- Set
behindReverseProxy: trueif behind nginx/Apache.
See admin/security.md for the full security guide.