Skip to content
Error codes · Monitors, checks & agents

RU-3014: Monitor authentication not available

This monitor cannot carry authentication right now: authenticated monitors run from a private location, on http monitors, on Pro and above, and the location's agent must be version 0.4.0 or later so it can resolve secret references. Removing authentication is always allowed.

Where it is raised

  • PATCH /api/v1/checks/{id}/auth

What triggers it

The refusal names the first of four conditions that failed, checked in this order: the monitor is not http, it does not run from a private location, the account's tier is below Pro, or the agent at the monitor's location is older than 0.4.0. Every other location the monitor runs from is checked for the same agent version after that.

Example response

PATCH /api/v1/checks/{id}/auth
HTTP 403

{
  "error": "Update the agent at <location> to version 0.4.0 or later to send credentials. An older agent cannot resolve secret references.",
  "code": "RU-3014"
}

Common causes

  • The account is on Free.
  • The monitor runs from RealUptime's regions rather than a private location, or is not an http monitor.
  • The location's agent is older than 0.4.0, or has not checked in since it was updated.

How to fix it

  1. Upgrade Monitor to Pro or above.
  2. Update the agent on the location's machine to 0.4.0 or later and let it check in once.
  3. Run the monitor from a private location if the target is internal.

Related codes