FAQs

Bright Data uses cookies to remember your login credentials in order to keep your user experience at its best. If you are using third-party extensions that regularly removes cookies from your device then you’ll see the login message quite often.

Browser extension does not yet support the new SSL certificate (which works with port 33335). Support for new certificate will be introduced soon and then you can work with the new certificate.

In the top right corner you can click on “Delete Cookies”. This will delete all the cookies from your device except Bright Data’s and Google’s cookies so you could keep using our service with no interruptions and keep your browser extensions alive.

Yes!

Bright Data extension works on both regular and incognito mode.

To enable incognito support on Chrome, do the following:

• Type chrome://extensions in the chrome address bar
• Make sure Allow in incognito is checked

Custom headers are mainly meant to make the request more specific. You should use it in cases when you need to pass custom parameters with your requests to the target site. Every header should contain Name & Value and you can add as many headers as you like.

There are few possible reasons for proxy error when setting up the extension:

• A zone was not selected. Make sure that the form is filled correctly.
• Your account is ‘disabled’. You can easily check this on your Dashboard.
• You have a negative balance. Check this in your Billing section.
• Bright Data network status issues. You can check the network live status here.

No. The Scraping Browser is not a proxy product, and is not compatible with the extension.

Yes. there is no limit on how many extensions are logging to the same account.

Yes!

They will need to go to the extension setup page and login with the customer name, zone name and zone key of the zone you wish to let them access. All the zone info is available in the Zones section.

You can also use this link in order to automatically insert your guest-login credentials:

https://brightdata.com/cp/bext?customer=customer_id&zone=zone_name&key=ZONE-KEY

This workflow is relevant to allow access to the Proxy Manager when integrated with a browser. The access is granted by updating the config file of the proxy manager.

This can be done by sending the next API command:

curl -X POST "http://<remote-server-IP>:22999/api/proxies" -v -H "Content-Type: application/json" -d '{ "proxy": { "customer": "<account_ID>", "zone": "<zone>", "password":"<zone_password>", "multiply_users": true, "users": ["<email>"], "bw_limit": { "days": 100000, "bytes": 9000000000 } }, "create_users": true }'

1. Change remote-server-IP with the server IP address of where the proxy manager is installed or 127.0.0.1 if it is installed locally.
2. Change account_ID with your Account ID on the settings page
3. Change zone>, zone_password` with the relevant access parameters from the zone page
4. Change email with the user’s email.

Once the command will be sent, a detailed email with instructions and credentials will be sent to email.

In the API output, the user’s password is also provided along with additional information such as the port number. It can be seen in the next example:

The user can now access the proxy by installing the extension.

5. After installation select “Connect through proxy manager”

6. Enter the IP address of the Proxy Manager server along with the relevant port for example:

7. Select done. Then, click “Sign in”.

8. Enter the credentials Received.