Skip to content

Connect a server

Connecting a server follows the same flow for every game we support. You install a small agent (or drop in a game-specific resource), give it your panel key, and restart the server once. The agent dials out to the panel over its own outbound connection, so you never open an inbound port or touch your firewall. Within a few seconds the server shows up in the panel with live players, CPU, memory, and uptime.

Get your panel key

Every server authenticates with a panel key. It looks like this:

gm_live_xxxx

Open the panel, create a server entry, and copy the key it generates. Each server gets its own key. Treat it like a credential: anyone with the key can report data into that server slot, so keep it out of public repos and shared logs.

Connect with the agent (works for every game)

The universal path is the install command. Run it on the machine where your game server already runs, then paste the key when prompted.

  1. 1Run the installer on the server host: curl -fsSL https://get.gamemanage.net | sh
  2. 2Paste your panel key (gm_live_xxxx) when the installer asks for it.
  3. 3Restart your game server once so the agent attaches and starts reporting.
  4. 4Watch the panel: the server appears within a few seconds and switches to online.
curl -fsSL https://get.gamemanage.net | sh

Connect with a game-specific resource

Some games connect through a resource or plugin instead of the standalone agent. The flow is identical: add the resource, paste the same panel key into its config, restart once, and the server reports in. The only thing that changes per game is where the files live and what the config file is called.

  • FiveM and RedM: add the panel resource to your resources folder and start it from your server config.
  • Rust, CS2, Minecraft Java, and Palworld: drop in the plugin or agent for that server and set your key in its config.
  • For exact paths and filenames, see the per-game page under Getting started for the server you run.

Note: Restart the server once after pasting the key, not just the resource. The agent attaches on a full restart, so a hot-reload or config refresh alone may not register it. If the server does not appear in the panel within a minute, confirm the key has no trailing whitespace and that the host can make outbound HTTPS connections.

Confirm it worked

Once the server is online in the panel you have live monitoring, the streaming console, and config and file editing for that server. From here you can set up scheduled backups, invite teammates with per-server roles, and review the audit log. To connect more servers, repeat the same flow with a new panel key for each one.

Next →Paste your panel key
Still stuck? Ask in Discord or contact the team.