Allocations

Allocations are IP and port combinations assigned to nodes that game servers use for network connections. Every game server needs at least one allocation to accept player connections.

---

What Are Allocations?

An allocation is an IP:port pair on a node. When you create a game server, it binds to its assigned allocation so players can connect. For example, an allocation of 192.168.1.10:25565 means the game server listens on that IP address and port.

Each allocation can only be used by one server at a time.

---

Adding Allocations to a Node

1. Navigate to Admin > Nodes and select a node.
2. Go to the Allocations tab.
3. Enter the IP address and port(s) to add.

Single Ports

Enter individual ports separated by commas:

25565, 25566, 25567

Port Ranges

Use a dash to specify a range of ports:

25565-25600

This creates 36 individual allocations, one for each port in the range.

Using 0.0.0.0

Setting the IP to 0.0.0.0 binds the allocation to all network interfaces on the node. This is the most common choice when:

• The node has a single public IP
• You want the server accessible on all interfaces
• You are behind a NAT or proxy

If your node has multiple IPs and you want to control which one a server uses, specify the exact IP address instead.

---

Global Allocations View

The Admin > Allocations page shows all allocations across all nodes in one place. Use this view to:

• See the total number of allocations in your panel
• Find which node and server an allocation belongs to
• Identify unassigned allocations

Filtering and Searching

You can filter allocations by:

• Node - show allocations for a specific node only
• IP address - find allocations on a particular IP
• Port - search for a specific port number
• Status - filter by assigned or unassigned

---

Primary vs Additional Allocations

Each server has one primary allocation and can have multiple additional allocations.

• Primary allocation - the main connection address shown to players. This is the address displayed on the server detail page and used as the default connection endpoint.
• Additional allocations - extra ports for features like RCON, query, or plugins that need separate ports. Some games require multiple ports (e.g., a game port and a query port).

The primary allocation is set when the server is created. You can change it later in the server settings.

---

Assigning Allocations to Servers

Allocations are assigned to servers in two ways:

1. During server creation - select a primary allocation (and optionally additional allocations) when creating the server.
2. After creation - add or change allocations in the server's Network tab.

An allocation must be on the same node as the server. You cannot assign an allocation from one node to a server on a different node.

---

Deleting Allocations

To delete an allocation:

1. The allocation must be unassigned - not in use by any server.
2. Navigate to the node's Allocations tab or the global Admin > Allocations page.
3. Select the allocation(s) and click Delete.

You cannot delete an allocation that is currently assigned to a server. Unassign it first by removing it from the server's network settings.

---

Firewall Considerations

Adding an allocation in the panel does not automatically open the port on the node's firewall. You must ensure that:

• The port is open in the node's firewall (iptables, ufw, firewalld, or Windows Firewall)
• Any external firewalls or security groups (e.g., cloud provider firewalls) allow traffic on the port
• Both TCP and UDP are allowed if the game requires it (most game servers use UDP for game traffic)

If players cannot connect to a server, check the firewall first.

---

Port Planning Strategies

Planning your port allocations in advance saves time and avoids conflicts.

Contiguous Ranges Per Game Type

Assign port ranges to specific game types for easy identification:

Game Type	Port Range
Minecraft	25565-25599
Rust	28015-28049
ARK	7777-7799
Valheim	2456-2479
General	27015-27099

Leave Gaps Between Ranges

Some games need multiple consecutive ports (e.g., game port + query port + RCON port). Leave room between ranges so you can expand later.

Document Your Scheme

Keep a record of which port ranges are for which purpose. This makes it easier to add capacity and troubleshoot connection issues.