Proxy errors troubleshooting
Explore the catalog of Bright Data HTTP errors, including error codes, descriptions, and actions to resolve common proxy issues.
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:
Field | Description | Examples | REST API Field Name |
---|---|---|---|
HTTP Error | The protocol error numbers | 404 or 502 | status_code |
x-brd-err-code | Bright data module and error code number | client_10001 | error_code |
x-brd-error | Bright data main error message | Authentication failed | error |
x-brd-err-msg | Bright data elaborated message and actions | Authentication failed. Check your credentials or your account status in https://brightdata.com/cp/settings/billing | error_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.
To see a more compact view with the header fields response only use the -i
option for curl:
Alternatively, you can use the nc
command to get the fields printed to screen:
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:
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
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:
Was this page helpful?