GuidesReference

Errors & status codes

What the gateway returns when something goes wrong, and what to do about it.

When the gateway itself rejects or can't complete a request, it answers with an HTTP status and an X-RiftIP-Error header naming the cause. Responses that come from the target are passed through untouched.

Status	`X-RiftIP-Error`	Meaning	What to do
`407`	`auth_failed`	Wrong username or password, or an unknown option	Check credentials and option spelling
`402`	`plan_exhausted`	No bandwidth, IPs or days left on the plan	Top up or renew in the dashboard
`403`	`target_restricted`	The target is restricted for your account	Contact support to request access
`429`	`concurrency_limit`	Too many requests in flight for your plan	Queue requests; retry with backoff
`502`	`exit_failed`	The exit couldn't connect to the target	Retry — you'll get a different exit
`504`	`target_timeout`	The target didn't answer in time	Retry, or raise your client timeout
`522`	`no_exit_available`	No exit matches your targeting right now	Widen targeting or retry later

#Retrying well

Retry 502, 504 and 522 with exponential backoff — a new attempt usually gets a new exit.
Don't retry 407, 402 or 403 automatically; they won't succeed until something changes.
For 429, slow down rather than retrying harder.

Note

Status codes from the target — a 403 from the website itself, say — have no X-RiftIP-Error header. That's how to tell a block from a gateway problem.