< Back to list
Let’s Start with proxy network dataflow.
The access point consists of a crawler sending HTTP or HTTPS request via an API, automated browser or a curl command directly to the Super Proxy.
The Super Proxy is a network load balancing server that routes the request to one of the available IPs in the Luminati proxy network. Luminati’s Super Proxy address is
zproxy.luminati.io and port 22225.
Ideally, the request is sent to the Luminati Proxy Manager which act as the middle man between your crawler and the Super Proxies helping you to control your traffic to the Super Proxies and manipulate the requests.
The Super Proxy strips down your IP and network details and routes the request to the desired exit node on the proxy network, which is also called proxy peer.
Luminati offers multiple networks including our data-center network, Residential network and Mobile network.
Our data center consists of dedicated or shared IPs from a large variety of subnets in multiple locations across the globe.
Our Residential network consists of real-user PC IPs that were allocated by an ISP.
The residential IPs can be shared, dedicated and or static. Static residential IPs are real ISP IPs that stay connected for unlimited time and do not change.
Our Static residential IPs are good for social and e-commerce account management that require maintaining the same IP for a long period of time.
Luminati has an SDK (software development kit) that is implemented into applications.
Luminati SDK provides an alternative to advertisements by providing the app user with the choice to opt-in to Luminati’s network instead.
To become a peer, three conditions must be met, the device must be idle (not-in-use), connected to the internet and plugged into a power source (or battery power over 60%).
Once an application owner includes Luminati SDK within their application the end user will get a message that clearly asks whether the user would like to opt-in to the Luminati Network instead of subscribing or seeing advertisements.
Most of the app or software users will prefer to improve their user experience by removing ads, thus the opt-in conversion rate to the Luminati network is very high. The users can choose to opt out at any time.
The end user is merely a tunnel exit node which means that Luminati does not collect any information or data.
This also means that the traffic routed through the user's device or exit node is transparent.
This is the same tunnel used by an ISP that routes traffic and ensures the end users is not susceptible to malware.
Partners that have integrated Luminati’s SDK have seen an increase in retention as well as user-engagement by offering an alternative to subscriptions and advertisements.
The Luminati mobile network was created in the same fashion as the residential Network but rather than a pc, it is an android device.
Now let’s get back to the journey of a single request through the Luminati network: A request is sent from a crawler or API to the Proxy Manager.
The Proxy Manager manipulates the request as defined and routes it to the relevant Super Proxy.
The Super proxy strips down the IP origin and includes the rules specified in the Proxy Manager then it routes the request to the relevant network and to the exit node.
The response request is received in the same manner.
First to the user device, then the super proxy and then to the proxy manager to log the request details and to check if certain rules need to be applied such as routing through a different network, geolocation, etc. before sending it back to your crawler.
The Luminati Proxy Manager is an open source software enabling you to control your entire proxy operation through an easy-to-use interface.
Within the proxy manager, you can create multiple proxy ports and define specific rules and conditions for each one.
You may find that many of your development efforts as well as investments in R&D can be easily solved using the Luminati Proxy Manager.
You can watch our previous webinar onBecome a Proxy Manager Expert
The Proxy Manager is a gateway for you to control, manipulate and monitor your scraping operations and again is installed locally on your operational servers.
The proxy manager can be installed on Windows, Linux and Mac machines and is also available as a docker image.
After installation of the Proxy Manager, you should open the ports in your firewall and router for the specific ports you created in the Proxy Manager.
The default port created in the Proxy Manager is port 24000 and as you create multiple ports it increase from there such as 24001, 24002, etc.
For checking if the firewall is enabled run
sudo ufw status in the CMD.
Next, follow the instructions based on the operating system you are using.
For example, if you are using Windows, go to the Control Panel, click Network and then click Internet Connections, and here you can find and open Windows Firewall.
Merely click the ‘Exceptions tab’, and then click ‘Add Port’, and begin to add the LPM ports.
You can also find a link to a windows tutorial in the Luminati FAQ for opening a firewall port.
Make sure to follow your specific router instructions for enabling internet access and open the relevant ports for the Proxy Manager.
The Proxy Manager can be installed on multiple machines when several users access the proxy network.
Once you have completed configuring the Proxy Manager port settings and rules, you can easily copy and paste the configuration file into your other installed proxy managers.
To do this go to the Manual configuration tab, copy the code in its entirety and past it into the other Proxy Manager.
If you use Linux you can take a configuration file that is already working on one machine and copy it to the rest of your servers using the following command:
scp [file_name].json root@[Remote_server]:/ root/.luminati.json
When installing on a remote server, Login as 'root' to the remote server Install Nodejs.
When the installation is completed, then run
node -v and
npm -v to see the nodejs and npm versions to ensure they have been installed as expected.
Install NPM if it is missing.
Next, install the Proxy Manager as instructed earlier taking into account which operating system you are using.
Now set up the server to accept remote connections as described earlier as this will enable firewall ports and configure the ports you need on your remote Proxy Manager.
Finally, test your set-up by sending requests to the configured ports from your local machine by using
curl --proxy 22.214.171.124:24000 "http://example.com"
In case you need to install the Proxy Manager on multiple remote servers, it is highly recommended you use the Proxy manager's Docker image as this will allow you to configure all of them separately.
It is important to ensure that Luminati Proxy Manager is only accessible when working in environments that are strictly under your control, or via a secured connection such as VPN.
Make sure to control access and block unwanted sources from accessing and using the Proxy Manager.
This is done by whitelisting specific IPs, within the individual ports in the Proxy Manager.
To do this, go to the Proxy Manager dashboard and select the relevant proxy port.
Then go to the general tab and add the whitelisted IPs.
In addition to IP whitelisting the administrator can set user permissions found on the Luminati control panel.
Merely, select each user permission whether they are a limited user or an admin who has permission to view everything including billing information.
In order to keep your traffic private, you should use HTTPS requests at all times.
To enable the debugging logs and proxy manager rules using HTTPS, make sure to download the certificate key and follow the instructions per browser on each and every machine the Proxy Manager is installed on.
Luminati‘s compliance process explicitly ensures that the users acquired through the Luminati SDK opt-in to our network, are fully aware that we share their resources, are provided a benefit in return and can opt-out at any time.
To access the residential network itself a user has to pass our thorough Luminati KYC which stands for Know Your Customer.
The KYC begins by requiring the customer to identify themselves by providing personal details and company details, and why they would like to use the network.
Luminati compliance team validates the supplied data and only once the customer’s identity and use case are approved will access to the residential network be enabled.
If the Luminati compliance team encounters a breach of our TOS (terms of service) by one of our users, the account is immediately disabled and can be reported to the relevant authorities if necessary.
Luminati customers are instructed to use HTTPS requests to avoid interception and all of Luminati’s products utilize SSL and are hard encrypted.
Luminati deletes network logs after 48 hours and only uses them for security and debugging purposes.
The networks logs include only the IPs, target websites and whether the request succeeded or failed.
All other customers data that saved is only for billing purposes such as the amount of traffic.
The billing data is saved with our payment service provider who complies with PCI and DSS security standards.
We do not share any of our customer information with 3rd parties or partners.
For specific questions feel free to ask in the small chat box at the bottom of the screen or reach out to your personal account manager.