ip_not_allowed

HTTP 403ip_not_allowedIP address not allowed

The key has an allowed IP list and the client's address is not on it.

Common causes

• a new server or a changed egress IP (NAT, cloud)
• a request from a development environment

What to do

• Add the IP address or CIDR block to the key's allowed IP list in the dashboard.

Retry?	No, the result will be the same unless the request changes.
Billing	0 units.
type	https://maticna.si/docs/errors/ip_not_allowed

Example response

HTTP/1.1 403
Content-Type: application/problem+json
X-Request-Id: req_01JB2Q8X6S7T

{
  "type": "https://maticna.si/docs/errors/ip_not_allowed",
  "title": "IP address not allowed",
  "status": 403,
  "detail": "The key has an allowed IP list and the client's address is not on it.",
  "instance": "/v1/entities/12345679",
  "code": "ip_not_allowed",
  "request_id": "req_01JB2Q8X6S7T"
}

Other errors with status 403

• insufficient_scope · Insufficient scope
• plan_upgrade_required · Plan upgrade required
• origin_not_allowed · Origin not allowed
• monitor_limit_reached · Monitor limit reached
• webhook_endpoint_limit_reached · Webhook endpoint limit reached

All errors