Set up Bright Data proxies

MaskPilot uses the standard connection parameters supplied by Bright Data. It does not require Proxy Manager or access to your Bright Data account. Prepare an active proxy zone first, then copy its host, port, username, and password.

Prepare Bright Data connection details

In the Bright Data dashboard, select a proxy network or zone and confirm its authentication, target location, and session policy. Obtain:

Common hosts and ports

Connection	Server	Port	Scope
Main HTTP / HTTPS entry	brd.superproxy.io	33335	Common main entry for datacenter, ISP, residential, and mobile proxy zones
Main SOCKS5 entry	brd.superproxy.io	22228	Bright Data proxy zones with SOCKS5 enabled
Dedicated IP, Proxy Manager, or dashboard-generated endpoint	Host shown in the dashboard	Port shown in the dashboard	Do not replace a dedicated endpoint with the main entry

33335 and 22228 are proxy-service entry ports, not target-site ports. SOCKS5 must use 22228; combining SOCKS5 with 33335 will fail. If the dashboard shows another host or port for the current zone, use that zone-specific value.

• The HTTP, HTTPS, or SOCKS5 connection protocol.
• The proxy host and the port assigned to that protocol.
• The zone username and zone password.
• Any session parameter required to keep one exit.

Do not use the website sign-in password in place of a zone password or copy example credentials from an article. Bright Data can use a different port for SOCKS5 and can require provider-side DNS resolution. Follow the current dashboard and the official Bright Data SOCKS5 guide.

Add one Bright Data proxy

1. Open Proxies in MaskPilot and select “Add proxy.”
2. Select “Standard proxy.”
3. Choose HTTP, HTTPS, or SOCKS5 according to the Bright Data zone.
4. Enter the proxy host, protocol-specific port, zone username, and zone password.
5. Set Provider to Bright Data and optionally record the zone purpose or session policy.
6. Save, select “Check connection,” and verify the exit location.

The Region field in MaskPilot is an inventory label. It does not change the Bright Data exit. Generate country, state, city, and sticky-session parameters in Bright Data first, or preserve them in the username exactly as the provider instructs.

Import several connections

After downloading or copying several endpoints from the dashboard, use Bulk import with one endpoint per line:

host:port:username:password
http://username:password@host:port
https://username:password@host:port
socks5://username:password@host:port

A line without a scheme is imported as HTTP. Keep an explicit protocol prefix for HTTPS or SOCKS5. If a username or password contains reserved characters such as @, :, or /, use the complete URL supplied by the dashboard or URL-encode the value. Review the protocol and port after import. Do not reuse an HTTP-zone port for SOCKS5 unless the current provider configuration says to do so.

Assign it and keep a session exit

1. Create or edit a browser profile.
2. Under Network connection, select “Use proxy.”
3. Select the required Bright Data node from the saved proxies.
4. Save and launch the profile, then verify the actual exit.

Rotating residential proxies can change IP by default. When one browser session requires a stable exit, add the provider-defined session parameter to the Bright Data connection before saving it in MaskPilot. A note or region label does not control rotation.

Common failure causes

• The website password was used instead of zone credentials.
• The HTTP, HTTPS, or SOCKS5 protocol does not match the selected port.
• The zone, country, or session parameter in the username is misspelled.
• Zone balance, traffic, allowlist, or compliance settings reject the connection.
• The current device cannot reach the provider entry or required DNS path.

Run the connection check again after changing one parameter. See Why does a proxy check fail? for diagnosis, or Add, import, and assign proxies for the complete import and assignment flow.