Docs
PricingDashboard

Platform errors

IP allowlist blocked (403)

When an endpoint has a non-empty IP allowlist, the gateway accepts only listed client IPs. Everyone else receives HTTP 403 before RPS checks and upstream forwarding.

HTTP 403-32000

← All errors

Example response

Example

HTTP/1.1 403 Forbidden
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": null,
  "error": {
    "code": -32000,
    "message": "client IP is not allowed for this endpoint"
  }
}

Causes

  • Allowlist is non-empty and the request IP is missing.
  • Egress IP changed (new NAT, cloud provider, VPN, or serverless region).
  • You added a private LAN IP while the gateway sees the public egress address.

How to fix

  • In the dashboard → Endpoints → Settings, add the real egress IPv4/IPv6 (exact addresses; no CIDR).
  • Clear the allowlist and save if you no longer need IP restriction.
  • Confirm which IP the gateway sees (Cloudflare / CDN headers when applicable).

Notes

  • Maximum 50 addresses per endpoint. Empty allowlist means all IPs are allowed.
  • See the full IP allowlist guide for header resolution details.

Related