What the networking tab does#
The Networking tab is where you control how players and web services reach your server. The panel describes it as the place to manage subdomains and the IP addresses and ports your server can bind to for incoming connections. It pulls together three things: the subdomain that gives your server a friendly address, a link to the proxy routes that put a web service behind a real URL, and the port allocations your server listens on.
An allocation is an IP and port written as IP:port. A server can hold several allocations, and one of them is marked as the primary. The primary feeds the SERVER_IP and SERVER_PORT variables your server reads at boot, so it is the address players type in to connect. See Startup for how those variables are used.
Reading and adding allocations#
Each allocation appears under "Port Allocations" with its IP and port. Click the IP:port to copy it to your clipboard. When an alias is set for the allocation, the panel shows alias:port in place of the raw IP, and that alias is what gets copied.
The badge next to the section header shows how you are placed against your plan. It reads as a count out of your limit such as 2 of 5, as 3 (unlimited) when there is no cap, or as a red Disabled badge when extra allocations are turned off for the server. The primary allocation does not count toward the limit, so it never eats into the extras you can add.
To add one, click "New Allocation". The port is picked for you at random and you cannot choose the number. Reach for a second allocation when a plugin or mod needs its own port, for example a voice chat service or a separate query port. Once you hit your limit the "New Allocation" button disappears until you free one up. If the server has no allocations at all yet, the list shows "No allocations found" with a prompt to create your first one.
Dedicated IPs#
If the server has a dedicated IP, the Port Allocations section works a little differently. The dedicated address is shown under the section heading, every allocation on it carries a green "Dedicated" badge, and the count badge reads as ports used out of the dedicated limit. Most importantly, the add button changes to "Add Port" and lets you type the exact port you want rather than taking a random one.
Clicking "Add Port" opens a small form with a single "Port Number" field. Enter a port between 1024 and 65535 and click "Add Port" to add it to your dedicated IP, or "Cancel" to back out. This is how you get memorable ports like 25565 for Java Edition or 19132 for Bedrock. When the dedicated IP has no ports left, the panel shows a "Dedicated IP port limit reached" notice and hides the Add Port button.
25565 or 19132.Notes and the primary allocation#
Every allocation has a notes field so you can record what a port is for. Click the notes box, which reads "Click to add notes..." when empty, type into the area (its placeholder is "Add notes for this allocation..."), then click "Save". "Cancel" discards the change and leaves the old note in place.
To change the address players connect to, click "Make Primary" on the allocation you want. The current primary carries a "Primary" badge, its "Make Primary" button is disabled, and it cannot be deleted while it holds that role. If you need to remove the allocation that is currently primary, promote a different one first, then delete the old address.
SERVER_IP and SERVER_PORT. Restart the server so it binds to the new address.Deleting works the same way for any non-primary allocation. Click "Delete", then confirm the "Are you sure you want to delete this allocation?" prompt. The "Delete" button stays disabled on the primary, which is the panel's way of stopping you from cutting off the address players rely on.
Subdomains#
Under "Subdomain Management" you can give your server a friendlier address than a raw IP. Type a label, then choose one of the two available domains from the dropdown next to it, pyro.social or pyro.lgbt, which gives you an address like myserver.pyro.social or myserver.pyro.lgbt. The panel checks whether the full name is free as you type. While it checks it shows "Checking availability...", then a green or red status line with the result. The "Create Subdomain" button stays disabled until the name is both valid and available.
The label has to follow a few rules:
1to63characters long.- Lowercase letters, numbers, and hyphens only.
- Must start and end with a letter or number.
Once a subdomain exists, the section switches to a display showing the current full domain along with an "Active" or "Inactive" status dot, and gives you "Edit Subdomain" and "Delete Subdomain" buttons. Editing opens the form again with "Cancel" and "Save Changes" so you can change the label or the domain. Deleting removes the subdomain along with all of its DNS records and cannot be undone, so the panel asks you to confirm first.
If you own a domain and want to point it at your server yourself, see Proxy routes.
Proxy routes#
Proxy routes put a web service that runs on your server behind a real URL, so you can open something like a Dynmap or BlueMap view, or any other web interface, without handing out an IP and port. The Networking page links through to "Proxy Routes" on its own screen, where you click "New Route" to open the "Create Proxy Route" dialog.
In the dialog you first pick an allocation, which is the internal port the route forwards traffic to. Then you choose a route type:
- Path-based, where the service lives under a path such as
/mapon your subdomain. - Subdomain, where a prefix such as
mapbecomes its own name in front of your server's subdomain, for examplemap.yourserver.pyro.social. - Custom domain, where you bring a domain you own such as
maps.example.comand optionally a path under it.
Path-based and subdomain routes need your server to have an active subdomain first, so set one up in the section above before you reach for them. Without one, those options are greyed out in the dropdown and labelled "(requires subdomain)", the dialog defaults to the custom domain type, and the Proxy Routes page shows a "Subdomain Required" notice.
A custom domain takes an extra step. After you create the route the panel shows a "Domain Verification Required" box with the DNS record to add at your registrar (its type, name, and value). Add that record, then click "Check Propagation". Once it passes, an SSL certificate is issued for the domain automatically and the route's status badge moves to active. If verification needs another attempt later, the route's menu offers "Retry Verification", which is rate limited so you may be asked to wait before trying again.
Each route shows a status badge of "Active", "Inactive", or "Disabled". Click the route's name to copy its full URL. The "..." menu on the row holds "Edit Route", "Enable Route" or "Disable Route" to toggle it, and "Delete Route", which asks you to confirm because it cannot be undone.