Your first server
Create your first game server, from an empty panel to players connecting.
Step 1: sign in
Open your panel domain in a browser, such as https://panel.example.com. Sign in with the administrator account you made during the installation.
Step 2: open the admin area
Click Admin Panel at the foot of the sidebar. Nodes, servers, games and users all live here.
Step 3: add a node
A node is a machine that runs game servers. It can be the panel server itself or a separate machine.
- Go to Admin > Nodes.
- Click Add Node.
- Fill in the form.
| Field | Description |
|---|---|
| Node Name | A name for this node, such as us-east-1. Required. |
| Description | A note for your own use. |
| FQDN / IP Address | The domain or IP of the node. Leave it blank to detect it. |
| Operating System | Linux or Windows. Linux nodes need Docker, which the install command adds for you. |
| Memory Limit (MB) | The memory the panel may hand out here. Leave it blank to detect it. |
| Disk Limit (MB) | The disk the panel may hand out here. Leave it blank to detect it. |
- Click Create Node.
The panel shows you an install command for this node. Copy it.
Step 4: install the daemon
The daemon is the agent that runs on a node and looks after its game servers. Your install command comes from your own panel and carries a registration token, so treat it as private.
Linux, as root:
curl -sSL "https://panel.example.com/api/nodes/install/YOUR_TOKEN" | sudo bashWindows, in PowerShell as Administrator:
irm 'https://panel.example.com/api/nodes/install/YOUR_TOKEN' | iexOn Windows the installer also opens port 8443 and port 2022 in the firewall.
WARNING
A registration token lasts 24 hours. If yours expires, open the node in the panel and make a new one.
Step 5: check the node is online
Go back to Admin > Nodes. The node reads Online once the daemon connects.
If it reads Pending Setup or Offline, work through these checks.
- Make sure the daemon is running on the node.
- Linux:
systemctl status badger-daemon - Windows:
Get-Service BadgerDaemon
- Linux:
- Make sure the node can reach your panel over HTTPS on port 443.
- Make sure no firewall blocks the node from reaching the panel.
- Read the daemon log.
- Linux:
tail -n 50 /var/log/badger-daemon/daemon.log - Windows:
Get-Content C:\BadgerDaemon\logs\daemon.log -Tail 50
- Linux:
Step 6: look at the games on offer
An egg is a template that tells the panel how to install and run one game. BadgerPanel ships with eggs for a long list of games.
- Go to Admin > Eggs to see them.
- Each egg carries the startup command, the install steps and the settings players can change.
- For a well-known game, use the egg that ships with the panel rather than writing your own.
Step 7: create the server
- Go to Admin > Servers.
- Click Create Server.
- Work through the seven steps of the wizard.
| Step | What you choose |
|---|---|
| 1. Owner | The user account that owns and runs this server. |
| 2. Node | The node the server runs on. |
| 3. Game | The egg for the game you want. |
| 4. Resources | The processor, memory and disk limits. |
| 5. Allocation | A free IP address and port on that node. |
| 6. Variables | The game settings the egg offers, such as the server name or version. |
| 7. Review | A summary of your choices. |
- Click the create button on the review step.
The server starts installing. Open its Console tab to watch. A small game installs in under a minute, and a game with a large download takes longer.
Step 8: start it and connect
- Open Servers in the sidebar and pick your server.
- Click Start.
- Read the console to check that it starts cleanly.
- Connect from the game, using the address and port on the Network tab.
Next steps
- Configuration to change how the panel behaves
- SSL certificates to manage your HTTPS certificate
- Updating to keep the panel and your nodes current
- Troubleshooting for the errors that come up most
