Skip to content
Error codes · Monitors, checks & agents

RU-3014: Check authentication not available

This check cannot carry authentication right now: authenticated checks run from a private location, on http monitors, on Growth 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.

On the wire

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

Common causes

  • The account is on the Free plan of both Status and Monitor.
  • The check runs from RealUptime's regions rather than a private location, or is not an http check.
  • 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 Status or Monitor to Growth 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 check from a private location if the target is internal.

Related codes

  • RU-3013: Invalid check authentication

Still stuck?

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