Connect a server

Add the public DayZ endpoint once and validate Steam Query and BattlEye RCON before the server joins the workspace.

Connection information

• Public address: the IP address or DNS name players can reach.
• Game port: the configured DayZ game port.
• Steam Query port: optional when discovery can determine it; enter it when your host uses a custom value.
• RCON port: the BattlEye RCON listener configured for this server.
• RCON password: a dedicated, strong credential stored through the protected server configuration flow.

Validate before saving

GAdmin first uses the public endpoint to identify the DayZ server and confirm that the expected services respond. A successful Steam Query check confirms the game-server endpoint. A successful RCON check confirms that the administrative endpoint and credential work.

Firewall and NAT

Your server firewall, provider firewall and edge routing must agree on the configured ports. Expose only the service ports required by your hosting arrangement. The GAdmin Agent calls the cloud through outbound HTTPS and does not require a new public inbound Agent port.

If discovery fails, verify that the public address is reachable from outside the server environment. A provider firewall, carrier-grade NAT or an incorrect forwarding rule can prevent the remote GAdmin service from reaching the endpoint.

After a successful save

GAdmin creates a workspace-scoped server record. Open Agent setup to generate the GAS- Server ID and gak_ API key used for pairing. The API key is tied to this server and is not interchangeable with credentials from another server in the workspace.

Rotating a server API key

Generate a replacement through Agent setup if the key may have been exposed. Rotation revokes the previous gak_ API key and the prior persistent Agent credential. Update GAdminAgent/Settings.json with the new value, then restart the Agent pairing flow.

Common validation failures

• The public and private addresses were confused.
• The game, Query or RCON ports were swapped.
• UDP/TCP rules do not match the service configuration.
• The server process or BattlEye RCON listener is not running.
• The RCON password differs from the active server configuration.
• A hosting-provider firewall still blocks the endpoint.

Continue with Troubleshooting when the portal cannot validate an endpoint that appears healthy in the server or provider control panel.