brightdata-common-errors

# Bright Data Common Errors ## Overview Diagnostic reference for the most common Bright Data proxy and API errors with real solutions and fix commands. ## Prerequisites - Bright Data zone configured - Proxy credentials available - Access to error logs ## Instructions ### Step 1: Identify the Error Check your proxy response status code or error message against the table below. ### Step 2: Apply the Fix Follow the specific solution for your error code. ## Error Reference ### 407 Proxy Authentication Required ``` HTTP/1.1 407 Proxy Authentication Required ``` **Cause:** Username format is wrong or credentials are invalid. **Fix:** ```bash # Verify credential format — must be exactly: # brd-customer-{CUSTOMER_ID}-zone-{ZONE_NAME} echo "Username: brd-customer-${BRIGHTDATA_CUSTOMER_ID}-zone-${BRIGHTDATA_ZONE}" # Test with curl curl -x "http://brd-customer-${BRIGHTDATA_CUSTOMER_ID}-zone-${BRIGHTDATA_ZONE}:${BRIGHTDATA_ZONE_PASSWORD}@brd.superproxy.io:33335" \ https://lumtest.com/myip.json ``` --- ### 502 Bad Gateway ``` HTTP/1.1 502 Bad Gateway X-Luminati-Error: target_site_blocked ``` **Cause:** Target site blocked the request despite Web Unlocker retries. **Fix:** - Increase timeout to 120s (Web Unlocker needs time to solve CAPTCHAs) - Switch to Scraping Browser zone for JS-heavy sites - Add `-country-us` to username for geo-specific content --- ### SSL Certificate Errors ``` Error: SSL: CERTIFICATE_VERIFY_FAILED ``` **Cause:** Missing Bright Data CA cert...