This article addresses all proxy errors originating from BrightData. While using our proxies, you may encounter errors that do not originate from Brightdata. To identify the source of the error, check if the response headers include BrightData error fields (seen below). Ensure you receive all response headers by following the instructions as seen below (-v flag).

If the error response lacks BrightData error header fields, the issue is unrelated to BrightData and instead you should refer to How to overcome website blocking.

​
Bright Data HTTP Errors

​
HTTP Header Fields

The following fields are returned upon and HTTP or HTTPS requests:

FieldDescriptionExamplesREST API Field Name
HTTP ErrorThe protocol error numbers404 or 502status_code
x-brd-err-codeBright data module and error code numberclient_10001error_code
x-brd-errorBright data main error messageAuthentication failederror
x-brd-err-msgBright data elaborated message and actionsAuthentication failed. Check your credentials or your account status in https://brightdata.com/cp/settings/billingerror_message

​
Getting HTTP header fields

​
Testing from command line

To view and test your settings, or restoring an issue, you can run a curl command from your shell prompt and add the option flag -v or i. These flags will run curl in verbose mode and print out the header fields, including the custom error code and message.

curl -v [rest of curl command options]

To see a more compact view with the header fields response only use the -i option for curl:

curl -i [rest of curl command options]

Alternatively, you can use the nc command to get the fields printed to screen:

echo "[tcp nc inputs]" | nc -C -v brd.superproxy.io 33335

nc inputs may include “empty” lines, those are essential for correct testing using nc command

​
curl Command snippet

curl command snippet, with all required zone parameters is available in the Overview tab in Bright Data control panel for the zone you are working on.

​
Accessing via programming language

Bright Data HTTP header fields can be accessed thru your programming language, as any other HTTP header field.

​
Accessing via Bright Data’s Proxy REST API

Bright data offers a REST API to access its proxy networks as well as the Unlocker product and our SERP for targeting search engines. The error field names are slightly different , yet the content is identical.

Example response:

"status_code": 407,
"status_message": "Proxy Authentication Required",
"error": "Proxy Authentication Required",
"error_message": "No proxy credentials provided. Please add credentials and try again.",
"error_code": "client_10010"

​
Error Catalog

​
HTTP Error 400

When Using the Data center/ISP or gIPs products with the -ip-x.x.x.x targeting flag, the error code 400 can appear in case the IPs under your zone has been refreshed, removed, or simply changed due to system updates

This error typically arises after your BrightData account has been recently suspended. An automatic suspension occurs if your account balance becomes negative. If the suspension extends beyond 24 hours, the static allocated IPs will be released from your account. Upon reactivation, the reallocated IPs may differ from the original ones, thus if the previously allocated IPs are still being targeted - this error is thrown.

Whenever this error appears, you should go to your Bright Data Zones page, and view the updated list of IPs relevant to this zone.

​
HTTP Error 401

These are the x-brd-err-code values for HTTP error 401:

​
HTTP Error 402

These are the x-brd-err-code values for HTTP error 402:

​
HTTP Error 403

HTTP 403 response code means you are forbidden from accessing a valid URL. The server processed the request, but it can’t fulfill the request either due to the way the request was sent by the client or due to Bright Data policy, blocking target access.

These are the x-brd-err-code values for HTTP error 403:

​
HTTP Error 407

If you get HTTP error 407, this implies there is an error in authentication. This can be due to incorrect credentials or due to your account being suspended.

​
HTTP Error 429

These are the x-brd-err-code values for HTTP error 429:

​
HTTP Error 502

These are the x-brd-err-code values for HTTP error 502: