Nodes are the Wings daemons that actually run your game servers. Locations are logical labels used to group nodes — for example, by data center region. Every node belongs to exactly one location, and every server runs on exactly one node.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/calagopus/panel/llms.txt
Use this file to discover all available pages before exploring further.
Locations
Locations provide a way to organize nodes by geography or purpose. When you create a server through the admin panel, you can filter the node list by location to place the server in the right region.Create a location
Click Create and enter a short name such as
us-east or eu-west. Add an optional description for clarity.Nodes
A node represents a single Wings daemon installation. Calagopus communicates with Wings over the node’s configured URL to start, stop, and transfer servers.Adding a node
Set the URL
Enter the internal URL Calagopus uses to reach Wings (for example,
https://node1.example.com:8080). This URL is used for API communication and is not exposed to end users.Set the public URL (optional)
If Wings is behind a reverse proxy or uses a different address for WebSocket connections and file downloads, enter that address in Public URL. Leave this blank to use the same URL as the internal URL.
Set resource limits
Enter the total Memory and Disk available on the node. These values are used to calculate how much capacity remains when assigning resource limits to new servers.
Node configuration
After creating a node, navigate to its Configuration tab to get the Wings configuration. This tab shows a generated YAML snippet that you paste into/etc/pterodactyl/config.yml on the Wings host, or you can copy the one-liner command that does this automatically.
The page also exposes a Live Configuration editor that connects directly to the running Wings daemon and lets you view and save its current config.yml without leaving the browser.
Resetting the auth token
If a node’s authentication token is compromised or you need to re-pair it, go to the node’s General tab and click Reset Token. Calagopus generates a new token and displays the updated configuration. You must update Wings with the new token before it can reconnect.Deployment and maintenance modes
Two toggles on the node’s General tab control availability:| Toggle | Effect |
|---|---|
| Deployment Enabled | When off, new servers cannot be assigned to this node. Existing servers are unaffected. |
| Maintenance Enabled | Flags the node as under maintenance. Useful for scheduled downtime. |
Wings proxy
When Public URL is left blank on a node, Calagopus can optionally route WebSocket connections and file downloads through the panel itself using the Wings Proxy feature. To enable this, click the globe icon next to the Public URL field on the node’s General tab. This fills in a proxy URL of the formhttps://your-panel/wings-proxy/<node-uuid>.
The Wings Proxy is useful when Wings nodes are on a private network that end users cannot reach directly. All traffic is forwarded through the panel, which does add latency.
Allocations
An allocation is a single IP:port combination that can be assigned to a server as its network binding. Allocations are managed per node.Create allocations
Click Create and enter an IP address along with one or more ports or port ranges (for example,
25565 or 25565-25575). Each combination becomes a separate allocation entry.Ctrl+A to select all, and then delete them in bulk using the action bar that appears.