Proxy errors troubleshooting
Explore the catalog of Bright Data HTTP errors, including error codes, descriptions, and actions to resolve common proxy issues.
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.
x-brd-err-code | x-brd-error | x-brd-err-msg |
---|---|---|
client_10060 | Proxy Error: ip_requested_not_allocated_by_customer | Requested IP ##.##.##.## is not allocated to this zone. Select an IP that is allocated to this zone or skip the -ip parameter in proxy username |
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.
x-brd-err-code | x-brd-error | x-brd-err-msg |
---|---|---|
client_10000 | Authentication failed | Invalid authentication: check credentials and retry. Bright Data credentials include your account ID, zone name and password |
client_10001 | Invalid Auth | Invalid authentication: check credentials and retry |
client_10010 | Proxy Authentication Required | No proxy credentials provided. Please add credentials and try again. |
client_10020 | Account is suspended. Login to brightdata.com/cp/setting/billing to activate your account | Account is suspended. Login to https://brightdata.com/cp/setting/billing) to activate your account |
client_10030 | Authentication failed | You are not allowed to access our API via this IP. Please verify your settings or whitelist this IP. |
client_10040 | KYC Required. Please visit http://brighdata.com/cp/kyc and ensure you are verified | KYC Required. Please visit http://brighdata.com/cp/kyc and ensure you are verified |
policy_20120 | IP parameter <IP> is incorrect, use correct format in the IP parameter | IP parameter <IP> is incorrect, use x-luminati-ip header format in the IP parameter |
HTTP Error 401
x-brd-err-code | x-brd-error | x-brd-err-msg |
---|---|---|
client_10050 | Auth failed: IP blacklisted [IP] | Auth Failed IP blacklisted: [IP]. Check FAQ: how to blacklist/whitelist ips and domains? to resolve |
HTTP Error 403
x-brd-err-code | x-brd-error | x-brd-err-msg |
---|---|---|
client_10070 | No Protocol | Protocol was missing from original request. Please add either HTTP or HTTPS and retry. |
client_10080 | No Destination Host | No destination host. Destination host is missing or incorrect. Check your request parameters and try again |
client_10090 | You are trying to use Scraping Browser zone as regular proxy | You are trying to use Scraping Browser zone as regular proxy. A browser should be used to access this zone. See https://docs.brightdata.com/scraping-automation/scraping-browser/introduction for information on how to access your scraping browser zone |
policy_20010 | Bad protocol | The protocol you are using to access our proxy is not supported. Bright data supports HTTP, HTTPS & SOCKS5 upon special approval. Please fix your protocol and try again |
policy_20020 | Bad port | Bad Port used. Ports we support: https://docs.brightdata.com/proxy-networks/faqs#how-to-see-supported-ports-and-protocols |
policy_20050 | Forbidden: target site requires special permission. Contact BrightData for assistance | Forbidden: target site requires special permission. You are trying to access a target site which is not permitted by our compliance policy. In order to gain access you may need to undergo a KYC process, you can do so by filling in the form: https://brightdata.com/cp/kyc
If you have already completed the KYC approval, please contact your account manager for further details. |
policy_20051 | Forbidden: target site requires special permission. Contact BrightData for assistance | Forbidden: target site requires is a government site and requires special permissions to access. In order to gain access you may need to undergo a KYC process, you can do so by filling in the form: https://brightdata.com/cp/kyc
If you have already completed the KYC approval, please contact your account manager for further details. |
policy_20080 | Forbidden: request needs to be made using residential network | Forbidden: You are accessing a domain which is not permitted to access by Bright Data Datacenter or ISP networks. Please retry your request using a Residential network zone. |
policy_20090 | Forbidden: requests to this domain are blocked using the proxy networks, please get access via a Web unlocker zone or IDE tools, or contact your account manager to assist | Forbidden: requests to this domain are blocked using the Datacenter, ISP and Residential proxy networks, please get access via a Web unlocker zone or IDE tools, or contact your account manager for further assistance |
client_10130 | Forbidden: this super proxy is allowed to be used only for China domains via China peers. Otherwise use brd.superproxy.io. For more details review the following: https://docs.brightdata.com/proxy-networks/mobile/faqs#how-to-browse-chinese-sites-by-using-chinese-residentials-ips | Forbidden: this super proxy is allowed to be used only for China domains via China peers. Otherwise use brd.superproxy.io. For more details review the following: https://docs.brightdata.com/proxy-networks/mobile/faqs#how-to-browse-chinese-sites-by-using-chinese-residentials-ips |
policy_20030 | Forbidden: target blocked | Forbidden: You tried to target www.somehost.com but got blocked. It can be related to your blacklist or whitelist settings or the target site is not allowed by Bright Data policy. Read more: https://docs.brightdata.com/proxy-networks/faqs#what-is-error-code-403 |
policy_20000 | Access denied: <URL> is classified as <category> and blocked by Bright Data | Access denied: %URL% is classified as %CATEGORY% and blocked by Bright Data as it might breach Bright Data usage policy. For more details review the following: https://docs.brightdata.com/proxy-networks/residential/network-access#residential-proxy-network-policy |
policy_20230 | Country %COUNTRY% is not permitted for targeting, please modify to a different country | Country %COUNTRY% is not permitted for targeting, please modify to a different country |
policy_20240 | Proxy port %PORT% is restricted. Contact Bright Data support | Proxy port %PORT% is restricted. Contact Bright Data support |
HTTP Error 429
x-brd-err-code | x-brd-error | x-brd-err-msg |
---|---|---|
client_10110 | Your limited trial mode account exceeded the allowed rate limits. Add payment method to receive $5 credit and remove rate limits. You will not be charged | Your limited trial mode account exceeded the allowed rate limits. Add payment method to receive $5 credit and remove rate limits. You will not be charged |
policy_20220 | Requests rate to %URL% is too high | Rate limit for domain %DOMAIN% has been reached. Bright Data’s health monitor is throttling down these requests to prevent overloading of the target website. Reduce requests rate and try again or contact Brightdata.com for support |
policy_20221 | Requests rate to %URL% is too high | Rate limit for domain %DOMAIN% has been reached. Bright Data’s health monitor is throttling down these requests to prevent overloading of the target website. Reduce requests rate and try again or contact Brightdata.com for support |
HTTP Error 502
x-brd-err-code | x-brd-error | x-brd-err-msg |
---|---|---|
client_10120 | Block direct route | Request reroute blocked. You chose option not to reroute requests thru our superproxy on failure so reroute was blocked. To see more about this setting see: https://docs.brightdata.com/api-reference/proxy/request_error_handling |
peer_30030 | Proxy Error: We do not have proxies in the city you requested, | Proxy Error: We do not have proxies in the city you requested, please check the spelling or try again later. Check https://docs.brightdata.com/proxy-networks/faqs#how-to-target-a-specific-city for proper use of city targeting. |
policy_20130 | Residential Failed (bad_endpoint) - Requested site is not available for immediate residential (no KYC) access mode due to the fact that %HTTP_METHOD% requests are not allowed. To get full residential access for targeting this site, Fill in the KYC form: https://brightdata.com/cp/kyc | Residential Failed (bad_endpoint) - Requested site is not available for immediate residential (no KYC) access mode due to the fact that %HTTP_METHOD% requests are not allowed. To get full residential access for targeting this site, Fill in the KYC form: https://brightdata.com/cp/kyc |
policy_20140 | Residential Failed (bad_endpoint) - Requested site is not available for immediate residential (no KYC) access mode in accordance with robots.txt. To get full residential access for targeting this site, Fill in the KYC form: https://brightdata.com/cp/kyc | Residential Failed (bad_endpoint) - Requested site is not available for immediate residential (no KYC) access mode in accordance with robots.txt. To get full residential access for targeting this site, Fill in the KYC form: https://brightdata.com/cp/kyc |
Was this page helpful?