Connect a node

A node lets Panel manage a game host. Install one Daemon on each game host.

Complete Panel setup and set APP_DOMAIN to a Panel address reachable by the node.

Trusted same-host connections can use http://127.0.0.1:3000; HTTPS is recommended for public connections. If Local Docker from one-click deployment is online, proceed to create a game server.

1. Get Daemon

Download the matching archive from the Daemon 1.2.0 release and extract it into a new directory.

Host	Release name	Docker required for game servers
Linux	gamex-v1.2.0-linux-ARCH-unsigned.tar.gz	Docker Engine
macOS	gamex-v1.2.0-darwin-ARCH-unsigned.tar.gz	Running Docker Desktop
Windows	gamex-v1.2.0-windows-ARCH-unsigned.zip	Docker Desktop with Linux containers

For ARCH, use amd64 for Intel/AMD or arm64 for ARM/Apple Silicon; see Daemon CLI for file verification.

2. Connect the host

1. As a Panel administrator, select Create node in Nodes.
2. Enter the name, host operating system, and Start at boot preference.
3. Copy the generated installation command.
4. Run it in the extracted Daemon directory on the target host: Linux uses sudo ./gamex, Windows uses administrator PowerShell, and macOS uses the account that runs its LaunchAgent.
5. Confirm the installer prompts and wait for the node to come online.

Use a separate node, identity, and state directory for each host, and keep short-lived enrollment tokens out of shared scripts and logs.

Daemon connects outward to Panel. You do not need separate inbound ports for Daemon, files, or terminals. Configure the game ports used by players separately.

3. Check readiness

Check that the node is online, inventory is current, and Docker status is Running.

Docker status	Action
Running	Ready to create a game server
Not installed	Install and start Docker
Unavailable	Start the engine and check its connection address
Permission denied	Check access for the Daemon service account
Error	Inspect the reported error and service logs
Awaiting report	Wait for the next inventory report

If the node is offline, run these commands from the extracted directory with the installation account and privileges:

./gamex daemon status
./gamex daemon doctor

Add sudo for a root-installed Linux service. On Windows, replace ./gamex with .\gamex.exe. Use the results to check the service, Panel address, system time, certificates, and network connection. Stop the service before restoring node state; see Upgrade and backup.

Docker status updates with the next inventory report; if inventory stays stale, inspect diagnostics and restart Daemon.

Pause new servers and view usage

Disabling new scheduling on a node blocks workspace creation, rebuilds, and repairs. Existing containers continue running. Re-enable scheduling before applying deployment changes on that node.

Resource history records usage about once per minute. Host readings are independent of Docker, and workspace usage includes the game service and Shell sessions. Offline periods and missing readings leave gaps, which do not mean zero usage.

Ports and connectivity

Ask the AI assistant to inspect node ports or check a workspace's published endpoint when troubleshooting. Node port queries require administrator access. Results have specific limits:

Check	What the result establishes
Node ports	Checks host TCP/UDP bindings and running containers' published ports; availability is temporary and does not reserve a port
Workspace endpoint	Compares saved publication with Docker and tests TCP from the Daemon host; does not prove public-internet reachability
UDP endpoint	Needs an application response to establish reachability; a port mapping alone is insufficient
Workspace network	Separates outbound DNS, TCP, TLS, and HTTPS failures from published game-port issues

Saving a deployment checks its ports. You cannot save if another service uses a port or availability is unknown. The workspace can reuse its own unchanged port bindings. Checks do not reserve ports, so a new conflict can still occur at startup.

Private-network isolation for workspace egress requires Linux. On other hosts, choose a supported network policy before deploying.

Host SSH console

1. Enable SSH on the game host and make sure Daemon can reach it at 127.0.0.1 on the selected port.
2. Open the node's SSH console and enter an account with a password or private key.
3. Check and confirm the host key before connecting.

Panel does not store SSH credentials or output. This console controls the whole game host; the workspace Terminal opens only its container.