Account
Policy
Privay & Security
Billing & Pricing
Usage Monitor
FAQs
Web Unlocker
HTTP error code 502 means “Bad Gateway”. This error occurs when you send a request to a URL, but the URL’s server receives an invalid response from another server that it depends on to fulfill the request.
Possible causes
- We currently do have not matching peers for your zone’s configuration, as they might already be in use with a different client, or unavailable for other reasons.
- The connection has been timed out due to inactivity.
- The connection has been closed by the host (target URL) side
Sample error 502 response
Request URL: SAMPLE_URL Request method: GET ***Status code: 502***
Super proxy IP: IP
Username: lum-customer-CUSTOMER_ID-zone-ZONE-country
Password: PASSWORD
Sent from: 127.0.0.1
Response headers
connection: keep-alive
date: Tue, 14 Feb 2023 08:49:16 GMT
keep-alive: timeout=5
transfer-encoding: chunked
x-lpm-port: 24000
x-luminati-error: waiting for selector ".price-container" failed: timeout 90000ms exceeded
***x-luminati-error-code: expect\_element***
x-request-id2: REQUEST_ID
Request headers
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36(KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36
host: SAMPLE_HOST
accept-encoding: gzip, deflate
Connection: keep-alive
HTTP 403 response code means you are forbidden from accessing a valid URL.
The server understands the request, but it can’t fulfill the request because of client-side issues.
Possible causes
- Your machine IP is not whitelisted. In order to learn how to whitelist an IP, please review the following article.
- The domain you try to access is blocked by Bright Data.
- The domain you try to access is not specified in your use case.
- Failed captcha response (relevant for Web Unlocker and SERP API).
- The domain you tried to access is blocked by the Target host settings of your zone (check your proxy zone’s Access Parameters)
Sample error 403 response
< HTTP/1.1 403 response status was rejected
< x-debug-req-id: SAMPLE_ID
< X-Luminati-Error: response status was rejected: 403 Forbidden
< X-Luminati-Error-Code: http_status
< Date: Wed, 22 Feb 2023 11:11:23 GMT
< Connection: keep-alive
< Keep-Alive: timeout=5
< Transfer-Encoding: chunked
The 403 X-luminati-error (Forbidden) indicates you are targeting a domain that is not allowed by Bright Data
This can be resolved by contacting the Bright data compliance team for approval.
As the Bright data compliance team reviews your use case and confirms - you will be informed that access is been added.
For better handling, it is advised to add your account manager to the ticket and inform him as well for your requirement
When error message:
You tried to target <host> but got blocked
Appears, contact the Bright data compliance team (compliance@brightdata.com) or from the ticketing system
Our compliance team will review your request to gain access to the particular domain