Skip to content
Error codes · Monitors, checks & agents

RU-3005: Agent request refused (opaque 404)

Monitor-agent and heartbeat endpoints answer a plain 404 for every failure: missing token, malformed token, unknown token, and revoked token are deliberately indistinguishable, because the token is a secret whose revocation status must not leak. There is no more specific code on the wire, by design.

On the wire

Ships with HTTP status 404, carrying "code": "RU-3005" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.

Common causes

  • The agent's token was revoked from the dashboard.
  • The token was mistyped or truncated in the agent's configuration.
  • The agent is pointed at the wrong endpoint URL.

How to fix it

  1. Check the agent's status on your monitoring dashboard: a revoked or missing agent shows there.
  2. Re-issue the agent token from the dashboard and update the agent's configuration.
  3. Confirm the agent's endpoint URL matches the install instructions at /docs/monitor-agent.

Still stuck?

Ask support and mention RU-3005: the code pins down the exact refusal path, so you skip the diagnostic back-and-forth.