Clicky

Bright Data (former Luminati)

Updated 2 days ago by Yelena

Related articles
Check out our list of recommended proxy providers and get amazing deals!

This page explains how to set up Multilogin with Bright Data proxy solution. Read more about Bright Data on our blog.

Bright Data zones

Before setting up Bright Data proxy with Multilogin, you first need to create zones in your Bright Data dashboard. A zone is a set of your proxy preferences.

  1. Log into your Bright Data dashboard
  2. Go to the "Zones" page and click "Add new zone"
  3. Set your preferences and click "Save": proxy type (datacenter, mobile or residential), targeting permissions (ASN, city, country) and your Bright Data pricing plan

Once a zone is created, click "Edit" → "Settings" and complete the following:

  1. Set up a username and a password and store them somewhere safe (they will be used for the Super proxy solution)
  2. Add your IP address to the "Whitelist IPs" section
If you need to access the proxy from multiple computers or have a dynamic IP, you can put "any" in this field.

Once a zone is created, you can start using Bright Data Proxy Manager or Super proxy.

Bright Data Proxy Manager

Bright Data Proxy Manager is a separate app that provides full control over your IP releases. Here are some of its most notable features:

  • Target proxy IPs by city, country, ASN and carrier
  • Control IP DNS resolvement records
  • Set custom proxification rules (e.g. exclude proxifying images to save bandwidth)
  • Set up IP release stickiness to keep the same IP for as long as possible
Creating a proxy in Proxy Manager
  1. Download the Proxy Manager and launch it on the same device on which Multilogin is installed
The Proxy Manager needs to be installed and running on each device on which you plan to use the proxy with Multilogin.
  1. Log into the Proxy Manager with your Bright Data account
  2. Click "New proxy" or "Start" if you are just starting out
  3. Select the proxy's pre-set configuration and click "Save". Choose "Long single session" if you want to keep the same IP for as long as possible
  4. You can now select the created proxy to configure additional settings (for other settings, visit Bright Data official documentation):
    1. Set the country, city, ASN and carrier of your IP releases in the "Targeting" section
    2. Set IP DNS resolvement records in the "Request speed" section
    3. Set custom proxification rules in the "Rules" section
  5. Once the proxy is configured, note its port (it will be used in Multilogin)
Setting up a Multilogin browser profile
  1. Go to the "Plugins" section
  2. Activate the Luminati proxy plugin
  3. Click "Create new" and go to the "Proxy" tab
  4. Select "Luminati" in "Connection type"
  5. Select "HTTP" in "Proxy type" (or SOCKS5 if your proxy is configured to run in SOCKS protocols)
  6. Put 127.0.0.1 into the "IP or host" field (your local proxy IP)
  7. Put your proxy port into the "Port" field
Paste the proxy details into the "IP or host" field in the format IP:port or host:port and other fields will be populated automatically.
  1. Click "Check proxy" → "Create profile" → "Start"

Bright Data Super proxy

Another way you can use Multilogin with Bright Data is by utilizing a Super proxy. In general terms, this is an entry node through which you connect to Bright Data servers. Once connected, the service will redirect all your traffic through an exit node of your choice. Unlike with the Proxy Manager, you don't need to install an additional app on your device. However, it comes at a cost of being able to control IP releases only to a certain extent.

  1. Go to the "Plugins" section
  2. Activate the Luminati proxy plugin
  3. Click "Create new" and go to the "Proxy" tab
  4. Select "Luminati" in "Connection type"
  5. Select "HTTP" in "Proxy type"
  6. Put zproxy.lum-superproxy.io into the "IP or host" field
  7. Put 22225 into the "Port" field
  8. Put your proxy Username (the one you got when you were setting up the zone) along with location prefixes (discussed further) into the "Username" field
  9. Put your proxy Password (the one you got when you were setting up the zone) into the "Password" field
Paste the proxy details into the "IP or host" field in the format IP:port:username:password or host:port:username:password and other fields will be populated automatically.
  1. Click "Check proxy" → "Create profile" → "Start"
Specifying IP locations

In order to have an IP address from a certain country or city, you need to add a prefix to your Super proxy username.

For example, if you want to access IPs in specific countries, you need to use the gen zone and your default username will look like this: lum-customer-Name-zone-gen. You will then need to add a prefix by following the example below:

  • to connect to the US, your username must have the following: lum-customer-Name-zone-gen-country-us
  • to connect to Brazil, your username must have the following: lum-customer-Name-zone-gen-country-br

If you want to access IPs in specific cities, you will be using the city zone and your default username will look like this: lum-customer-Name-zone-city. You will then need to add a prefix by following this example:

  • to connect to New York (US), your username must have the following: lum-customer-Name-zone-city-country-us-city-newyork
  • to connect to London (UK), your username must have the following: lum-customer-Name-zone-city-country-gb-city-london
Super proxy nuances

If you would like to use Bright Data Super proxy, you need to include a session prefix in order to avoid mismatches in browser profile and IP location data. It's recommended to use the rand prefix:

  • lum-customer-{your_customer_id}-zone-{your_zone}-session-rand39484

The value 39484 is used as an example. It is recommended to set different rand prefix values for each browser profile.

The glob_ prefix is not working correctly in Multilogin.

Troubleshooting

IP rotation fix

If you are using a static IP, but it still rotates, the Bright Data team has implemented the following fix for it. A new proxy parameter has been added, which should resolve the issue: "const". If const is provided with a proxy request, a session will never drop even if tunnel setup failed (only by timeout).

Here's an example of the const parameter usage (it can be used like any other parameter):

lum-customer-<cust>-zone-<zone>-session-<session>-const

Video on the topic

Check out our latest news, research and tutorials


Was this article helpful?