Getting started

Create the workspace in the remote GAdmin portal, validate the public server endpoints and pair the GAdmin Agent before enabling daily operations.

Before you begin

• Administrative access to the DayZ server or its hosting control panel.
• The server's public IP or hostname and game port.
• The BattlEye RCON port and password.
• Access to the DayZ -profiles directory.
• Outbound HTTPS access from the server environment to gadmin.cloud.

The DayZ server can be self-managed or operated by a hosting provider such as Nitrado. The portal workflow does not depend on the server's operating system because GAdmin is always accessed remotely through the browser.

1. Create and verify your account

Open Create workspace, enter your account details and complete the e-mail verification flow. Sign in and create or select the workspace that will own the server.

2. Add the DayZ server

Choose Add server in the portal. Enter the public endpoint, game port, RCON port and RCON password. If your Steam Query port differs from the discovered/default value, provide it explicitly.

Run connection validation. Do not continue until the server identity and the expected RCON endpoint pass. See Connect a server for network checks.

3. Generate the Agent settings

Open the server's Agent setup action. Generate the server-specific Server ID, which begins with GAS-, and API key, which begins with gak_. The API key is displayed as a secret; copy it directly into the server-side settings file and do not save it in chat or tickets.

4. Pair the GAdmin Agent

Start the GAdmin server-side component once so it creates <DayZ profiles>/GAdminAgent/Settings.json. Add the Server ID and API key, keep apiBaseUrl set to https://gadmin.cloud, then deploy or enable the Agent using the controls available for your server or hosting provider.

Follow the full Agent pairing guide, especially if more than one DayZ instance uses the same server environment.

5. Verify the control path

1. Confirm the portal shows the agent as connected.
2. Check that fresh player or map snapshot times advance while the server runs.
3. Open the live player list and compare it with the server.
4. Use a low-impact supported action, such as a controlled test message.
5. Confirm the result appears in the operation history.

6. Invite the team deliberately

Add members only after the owner has verified the workspace. Give each role the minimum capabilities needed for their job. Test a delegated account before relying on it during a live incident.