Skip to content
Error codes · Monitors, checks & agents

RU-3002: Monitor target refused

The URL you asked realuptime to monitor was refused by the target guard. realuptime only probes public destinations: private networks, loopback, and cloud metadata addresses are never probed.

On the wire

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

Common causes

  • The target resolves to a private, loopback, or link-local address.
  • An internal hostname that isn't reachable from the public internet.
  • An unsupported URL scheme.

How to fix it

  1. Point the check at the public address of the service.
  2. For hosts inside a private network, install the monitor agent on a machine that can reach them instead of a public check.

Related codes

  • RU-3001: Invalid check request
  • RU-3005: Agent request refused (opaque 404)

Still stuck?

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