How to Set Up Bright Data With Puppeteer
Discover how to enhance Puppeteer’s browser automation with Bright Data. This guide will walk you through setting up secure, anonymous proxies for smoother web scraping and data retrieval.
Expand to get your Bright Data Proxy Access Information
Expand to get your Bright Data Proxy Access Information
Your proxy access information
Bright Data proxies are grouped in “Proxy zones”. Each zone holds the configuration for the proxies it holds.
To get access to the proxy zone:
- Login to Bright Data control panel
- Select the proxy zone or setup a new one
- Click on the new zone name, and select the Overview tab.
- In the overview tab, under Access details you can find the proxy access details, and copy them to clipboard on click.
- You will need: Proxy Host, Proxy Port, Proxy Zone username and Proxy Zone password.
- Click on the copy icons to copy the text to your clipboard and paste in your tool’s proxy configuration.
Access Details Section Example
Residential proxy access
To access Bright Data’s Residential Proxies you will need to either get verified by our compliance team, or install a certificate. Read more…
Targeting search engines?
If you target a search engine like google, bing or yandex, you need a special Search Engine Results Page (SERP) proxy API. Use Bright Data SERP API to target search engines. Click here to read more about Bright Data SERP proxy API.
Correct setup of proxy test to avoid “PROXY ERROR”
In many tools you will see a “test proxy” function, which performs a conncectivity test to your proxy, and some add a geolocation test as well, to identify the location of the proxy.
To correctly test your proxy you should target those search queries to:
https://geo.brdtest.com/welcome.txt
.
Some tools use popular search engines (like google.com) as a default test target. Bright Data will block those requests and you tool will show proxy error although your proxy is perfectly fine.
If your proxy test fails, this is probably the reason. Make sure that your test domain is not a search engine (this is done in the tool configuration, and not controlled by Bright Data).
What is Puppeteer?
Think of Puppeteer as a remote control for headless browsers. With just a few lines of Node.js code, you can direct browsers to gather information, run tests, and automate routine actions. It’s all about turning tough, time-consuming workflows into quick, manageable steps.
Maintain a consistent IP throughout your browser session by using the -session
parameter in your username. This is essential because BrightData proxies default to rotating IPs with each request. Learn more
New users should begin with ISP or Data Center proxies, as residential proxies are incompatible with browser integration in Immediate-Access mode .
For use-cases related to account management, use a consistent static dedicated IP for each account you are managing. dedicated ISP proxies should be used for this.
How to Integrate Bright Data With Puppeteer
Getting Started
Before integrating Bright Data, ensure you have the essentials:
1. Node.js: Install the latest version from nodejs.org.
2. Project Setup: Use a code editor you prefer (such as VS Code) and initialize a Node.js project.
3. Puppeteer: Add Puppeteer to your project by running:
Retrieve Your Bright Data Credentials
Sign in to your Bright Data dashboard and note down your proxy details:
• Host
• Port
• Username
• Password
These credentials will let Puppeteer route traffic through Bright Data’s secure, anonymous proxy network.
Configure Puppeteer for Bright Data
To connect Puppeteer with Bright Data:
1. Set the Proxy Server: Add --proxy-server=[HOST]:[PORT]
to Puppeteer’s launch arguments.
2. Authenticate: Use page.authenticate()
in Puppeteer to provide your Bright Data username and password.
Example Code
Here’s a sample script to guide you:
With Bright Data proxies integrated into Puppeteer, you gain secure and private browsing for all your automated tasks. Enjoy smoother data collection, reduced detection risks, and a more reliable workflow—so you can focus on insights and results, not on technical roadblocks.