Where it is raised
POST /api/v1/checksPATCH /api/v1/checks/{id}
What triggers it
The target guard parses the url and refuses a scheme other than http and https, a port other than the defaults, 80, 443, 8080 and 8443, a missing hostname, and a hostname that resolves to a private or reserved address. Each refusal sends its own sentence. It runs after the interval, latency and region checks and just before the monitor limit, so a monitor with a good url but a bad interval answers the interval code first.
Example response
POST /api/v1/checks
HTTP 400
{
"error": "That target resolves to a private or reserved address and can't be used.",
"code": "RU-3002"
}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
- Point the monitor at the public address of the service.
- For hosts inside a private network, install the monitor agent on a machine that can reach them instead of a public monitor.