Performance VPS
Foundational VPS
VDS
Specialty Servers
Domain Names
Colocation
Sub-Users, Allocations, and Ports
Give friends panel access without sharing your login, and understand allocations, the primary port, and how to change which port your game listens on.
Two panel tabs come up as soon as a server has more than one person involved or more than one port to think about. Users lets a friend, moderator, or co-admin help run the server without ever touching your MyNobull login. Network shows the addresses and ports the game listens on, and lets you change which one is primary. Both are in the panel described in Access Your Game Server Panel.
Sub-users#
Your MyNobull credentials control billing and every service on your account, so they should never be shared. Sub-users solve the problem properly: each person gets their own login to this specific server with only the permissions you grant.
- Open the Users tab and click New User.
- Enter their email address. They receive an invitation to set their own password (or, if they already have a panel account, the server simply appears in their list).
- Choose permissions. Permissions are grouped by area: control (console commands, start, stop, restart), files (create, read, read contents, update, delete, archive, SFTP), backups (create, read, download, restore, delete), allocations, startup, databases, schedules, users, settings, and activity. Tick only what the role needs. Backup download and restore deserve particular care: download hands over every file on the server, and restore replaces the current files.
- Save. You can edit permissions or remove the user at any time from the same tab. Their access ends immediately.
A moderator usually needs console and power control only. A builder or modpack maintainer needs files and SFTP, and perhaps backups. Reserve settings, allocations, and user management for a co-owner you fully trust. Everyone should turn on two-factor authentication in their own panel account settings.
Allocations and ports#
An allocation is a combination of an IP address and a port assigned to your server. Players connect to the primary allocation, which by default is the lowest-numbered one; the game itself listens there. Games that need more than one port (a query port, an RCON port, a voice or web map port) use additional allocations, and each is listed on the Network tab with the same IP and its own port.
Change the primary port#
- Open the Network tab. Each allocation shows its IP, port, and an optional note field.
- Click Make Primary on the allocation you want the game to use.
- Restart the server. The game rebinds to the new primary port on start. Tell your players the new address, and update any DNS SRV record you use.
Need another allocation?#
Where your plan allows extra allocations, Create Allocation on the Network tab assigns a free port automatically; where it is not available for your product, open a ticket and say which game feature needs the extra port. You cannot delete the primary allocation itself; make another one primary first. Use the note field on each allocation to record what it is for ("RCON", "query", "web map"); future you will be grateful.
Sharing the address with players#
Players connect to IP:port. Ports other than the game's default must be given explicitly. To hide the port and the raw address behind a friendly name, create a DNS SRV record (Minecraft Java supports this natively) or simply publish play.example.com:port with an A record pointing at the allocation's IP.
