Verify & troubleshoot

Once the agent is running, confirm it’s reporting and know where to look if it isn’t.

Confirm it’s reporting

• Open the dashboard. Within a minute of the first collection, the server appears with a Health Score.
• Open Infrastructure and select the server — you should see live metrics, packages, services, domains and certificates.
• A single manual run prints a one-line summary:

demerzel-agent --once
# host-01 (Ubuntu 24.04) — host + 4 metric(s) + 812 package(s) + 3 domain(s) sent

Troubleshooting

“no identity — enroll first”

The agent can’t find a stored identity. Enroll the host (see Enroll a new agent), or make sure --config-dir points at the directory where you enrolled. Running as a different user than you enrolled with is the usual cause.

“enroll rejected (401): invalid_or_exhausted_token”

The token was already used, has expired, or was mistyped. Enrollment tokens are single-use — generate a fresh one.

Nothing shows up on the dashboard

• Check the service is running: systemctl status demerzel-agent.
• Check the host can reach app.demerzel.cloud over HTTPS (the agent is outbound-only — no inbound port is needed).
• Make sure you’re looking at the right organization — use the switcher at the top of the sidebar.
• Follow the logs: journalctl -u demerzel-agent -f.

Data looks stale

Each server’s page shows when it was last observed. If that timestamp stops advancing, the agent has stopped collecting — check the service and the interval.