Troubleshooting

Start with freshness and the narrowest failing layer. Preserve credentials, avoid duplicate actions and collect only the diagnostics needed for the problem.

Server validation fails

1. Confirm the public address, game port, Query port and RCON port have not been swapped.
2. Verify the DayZ process and BattlEye RCON listener are running.
3. Test that the endpoints are reachable from outside the server environment.
4. Review server, provider and router firewall/NAT rules.
5. Confirm the current RCON password matches the value entered in GAdmin.

Agent remains offline

• Check in the server or hosting control panel that the GAdmin Agent process or integration is running.
• Confirm outbound HTTPS to gadmin.cloud is allowed.
• Verify GAdminAgent/Settings.json belongs to the selected server, contains a GAS- Server ID and a gak_ API key, and has no extra whitespace inside either value.
• For multiple servers, confirm the Agent uses the intended -profiles directory.
• If the API key was rotated, update Settings.json and repeat the pairing flow.

Agent connects but players or map are stale

Separate agent heartbeat health from snapshot-source health. Confirm the DayZ-side component is updating map-snapshot.json in the same profiles directory used during installation. Check file modification time while the DayZ server is active.

If player state updates but map data does not, focus on the map snapshot producer and map-file path. If neither advances, focus on the selected profiles directory and server-side component.

Remote operation stays pending

1. Do not submit the same consequential action repeatedly.
2. Confirm the target Agent is connected and belongs to the same server.
3. Check that RCON is healthy in the server or hosting control panel.
4. Verify the signed-in member still has the required permission and entitlement.
5. Review the reported claim or completion state before retrying.

Browser workspace looks stale

Use a normal reload first. If another browser works, clear only GAdmin site data after signing out; do not erase unrelated browser data. Confirm the system clock is correct because session and CSRF protection depend on valid request state.

Useful support information

• Approximate time of the failure, including timezone.
• Affected server name or non-secret GAS- Server ID.
• Portal page and action that failed.
• Agent status and installed version.
• Whether Steam Query, RCON, heartbeat, players and map are independently healthy.
• Sanitized error text without keys, passwords, cookies or personal player data.