Your proxy failed

How to recognize it

The API answers with status 502 and a JSON body with the message and the error.code proxy_error, for example:

HTTP/1.1 502
Content-Type: application/json

{
  "error": {
    "code": "proxy_error",
    "message": "Your proxy could not be used: it could not be reached, refused the credentials or did not answer as a proxy."
  },
  "message": "Your proxy could not be used: it could not be reached, refused the credentials or did not answer as a proxy."
}

Common causes

• A wrong host, port or scheme in proxy (an HTTP proxy given as socks5, say), or a proxy that is down.
• A wrong user name or password, or @, : or / in them that are not percent-encoded.
• A proxy that accepts connections only from some IP addresses.
• The proxy could not reach the website, or refused it by its own rules.

How to fix it

1. Test the proxy from another machine, for example curl -x socks5h://user:password@proxy.example.com:1080 https://example.com.
2. Percent-encode @, : and / in the user name and password.
3. Put hosts that should not go through the proxy into proxy_bypass_hosts: they are loaded directly.

Retry

When the proxy works again. A retry right away usually fails the same way.

Billing

Not billed: a request answered with this error does not count against your quota. One exception: when an evaluate step of actions or the scripts ran in the page before the render failed, it is billed as one request, because that code could read the page, unless the failure is ours.

Related parameters

proxy, proxy_bypass_hosts. Each is described in the take endpoint reference.

Every response carries an X-Request-Id header. If this page does not explain the error, write to support@screenshotbase.com with that id. All statuses: status codes.