Check issues from the machine to the game: node connectivity → latest operation → game logs → port access. This sequence helps locate the cause without repeated starts or random changes.
Check the node
Open Monitoring and the intended machine. Check agent connectivity and available memory, CPU, and disk metrics. Missing recent data does not mean zero load.
If the node is unreachable, check its network and machine state with your provider first. A game command cannot repair a lost agent connection.
Find the latest operation
Open the task associated with the failure in the service or Activity. Record the action, time, state, and completion reason. Distinguish a waiting task from a completed failure.
Avoid repeatedly pressing start or apply while an operation runs. For settings and mods, check the previous change's result first.
Read game logs
Open the service's Logs. Look for the first error before the process stopped, not just the final line. Common causes include:
| Symptom | What to check |
|---|---|
| Game exits at startup | Version, distribution, and mod compatibility |
| Memory allocation fails | Free node memory and game settings |
| Data cannot be written | Free disk space and file paths |
| Game runs but players cannot join | Address, game port, and firewall |
| Setting has no effect | Draft application and required restart |
Linux diagnostics
With SSH access to the machine, these commands read the agent state and its journal. Run them on the node where the agent is installed.
sudo systemctl status gamehost-agent --no-pager
sudo journalctl -u gamehost-agent -n 100 --no-pager
Remove tokens, passwords, private addresses, and other sensitive data before sharing output. These commands do not replace checking game logs in the dashboard.
Incidents and notifications
An incident describes an observed issue. Inspect its context and linked resources. Configure available organization notification channels. Check incident state and notification delivery results separately.
Contact support
Include the service name or identifier, error time with timezone, action taken, task result, and relevant log lines. Explain what you expected and what happened.
Related guides: Connect a node, Game configuration, Player connections.