VMLogin Proxy Integration with Luminati
How to integrate VMLogin with Luminati
The first proxy service of a reverse proxy is considered the master (or parent) proxy. Subsequent proxy services can use domain-based, path-based, or virtual multi-homing, relative to the published DNS name of the master proxy service. If you are creating a second proxy service for a reverse proxy, see Using Multi-Homing to Access Multiple. Click Start then search for Luminati Proxy Manager. Wait until it boot. If a new browser window is not popping up, open a browser and navigate to 127.0.0.1:22999. Watch our tutorial video. Are you experiencing any problem with the Proxy Manager?
How to integrate VMLogin with Luminati
1.Download and install VMLogin（3 Days Free Trial），Download
2. Launch VMLogin and start with creating a new browser profile
3. Click ' Get random profile', then select the setting you want, like operating system, Screen Resolution, language, WebGL vendor, timezone, media device fingerprint etc.
4. Setting Proxy Server to your browser profile
5. Install and Launch Luminati Proxy Manager, then it will automatically open thehttp://127.0.0.1:22999/ browser interface for management.
6. Start to create proxy port
A. Login Lumitnati -> Start
B. Network-> Lumitnati, choose Luminati or External which you want. Opening rpt file.
C. Configuration-> Browser (Puppeteer/Selenium)
D. Create proxy port, then close.
7. Open and set your proxy, then text proxy, Fox example:
Proxy type: HTTP
IP address: 127.0.0.1
Multiple Proxy Manager Job
Port: 24000
8. If you need to open multiple ports, for each port should be in different IP address,you can enter the 24000 port to set it.
9. Generl-> Multiply proxy port-> select the number of port(such as 5), then open the button of 'Multiply proxy port per IP', click 'Select IPs', to select the port which is using.
Nginx HTTPS Reverse Proxy Overview
A Nginx HTTPS reverse proxy is an intermediary proxy service which takes a client request, passes it on to one or more servers, and subsequently delivers the server's response back to the client. While most common applications are able to run as web server on their own, the Nginx web server is able to provide a number of advanced features such as load balancing, TLS/SSL capabilities and acceleration that most specialized applications lack. By using a Nginx reverse proxy all applications can benefit from these features.
Benefits of Using a Nginx Reverse Proxy on an Instance
There are a important benefits of setting up a Nginx HTTPS reverse proxy:
- Load Balancing: A Nginx reverse proxy can perform load balancing which helps distribute client requests evenly across backend servers. It also improves redundancy as if one server goes down, the reverse proxy will simply reroute requests to a different server according to the routing policy.
- Increased Security: A Nginx reverse proxy also acts as a line of defense for your backend servers. Configuring a reverse proxy ensures that the identity of your backend servers remains unknown.
- Better Performance: Nginx has been known to perform better in delivering static content file and analyse URLs
- Easy Logging and Auditing: Since there is only one single point of access when a Nginx reverse proxy is implemented, this makes logging and auditing much simpler.
- Encrypted Connection By encrypting the connection between the client and the Nginx reverse Proxy with TLS, users profit from a encrypted and securized HTTPS connection, protecting their data.
Requirements:
- You have an account and are logged into console.scaleway.com
- You have configured your SSH Key
- You have sudo privileges or access to the root user.
- You have an web application running on a non-standard web port on the instance
- You have a compute instance running Ubuntu Bionic Beaver
- Make sure your domain name points towards your server ip (A or AAAA record)
Installing and Configuring Nginx
Note: This tutorial requires that you have already a web application running on your instance. You can for example install a lightweight web server like Webfsd, which runs on port 8000 by default to be joignable on the standard HTTP(s) ports via the proxy. If required it can be installed with apt install webfs
In the following example, we will configure an Nginx reverse proxy in front of an Apache web server. As a result, we assume that Apache is already installed and configured (on the same machine).
1 . Update the APT packet cache and install the Nginx web server via the packet manger:
2 . Disable the default virtual host, that is pre-configured when Nginx is istalled via Ubuntu's packet manager apt:
3 . Enter the directory /etc/nginx/sites-available and create a reverse proxy configuration file.
4 . Paste the following Nginx configuration in the text editor. The proxy server redirects all incomming connections on port 80 to the Webfsd server, listening on port 8000. Edit the port value depending on the applications specific port.
which returns
7 . Open a web browser on your local computer and paste your public_ip which will display your web applications homepage.
Adding TLS to your Nginx Reverse Proxy using Let's Encrypt
Multiple Proxy Manager Job
Important: Make sure your domain name points towards your server ip (A or AAAA record).
With the current setup, all incoming traffic on the standard, non-securized, HTTP port is anserwered by Nginx, which passes it to the web application on the instance.
For security reasons, it is recommended to add an encryption layer with TLS/SSL and to use HTTPS. Whilst it is technically possible to use self-signed certficates, it may cause very inconveniences as a warning is displayed by default in an users web browser when a self-signed certificate is used. A certificate authentity (CA) can issue trusted certificates which a recognized by most modern web browsers. The CA Let's Encrypt provides TLS certificate for free and the configuration of Nginx can be done easily with Certbot, a tool provided by the EFF.
1 . Install Certbot on your instance by using the APT packet manager:
2 . Certbot provides a plugin designed for the Nginx web server, automatizing most of the configuration work related with requesting, installing and managing the TLS certificate:
3 . Answer the prompts that display on the screen to request a valid Let's Encrypt TLS certificate:
2. Launch VMLogin and start with creating a new browser profile
3. Click ' Get random profile', then select the setting you want, like operating system, Screen Resolution, language, WebGL vendor, timezone, media device fingerprint etc.
4. Setting Proxy Server to your browser profile
5. Install and Launch Luminati Proxy Manager, then it will automatically open thehttp://127.0.0.1:22999/ browser interface for management.
6. Start to create proxy port
A. Login Lumitnati -> Start
B. Network-> Lumitnati, choose Luminati or External which you want. Opening rpt file.
C. Configuration-> Browser (Puppeteer/Selenium)
D. Create proxy port, then close.
7. Open and set your proxy, then text proxy, Fox example:
Proxy type: HTTP
IP address: 127.0.0.1
Multiple Proxy Manager Job
Port: 24000
8. If you need to open multiple ports, for each port should be in different IP address,you can enter the 24000 port to set it.
9. Generl-> Multiply proxy port-> select the number of port(such as 5), then open the button of 'Multiply proxy port per IP', click 'Select IPs', to select the port which is using.
Nginx HTTPS Reverse Proxy Overview
A Nginx HTTPS reverse proxy is an intermediary proxy service which takes a client request, passes it on to one or more servers, and subsequently delivers the server's response back to the client. While most common applications are able to run as web server on their own, the Nginx web server is able to provide a number of advanced features such as load balancing, TLS/SSL capabilities and acceleration that most specialized applications lack. By using a Nginx reverse proxy all applications can benefit from these features.
Benefits of Using a Nginx Reverse Proxy on an Instance
There are a important benefits of setting up a Nginx HTTPS reverse proxy:
- Load Balancing: A Nginx reverse proxy can perform load balancing which helps distribute client requests evenly across backend servers. It also improves redundancy as if one server goes down, the reverse proxy will simply reroute requests to a different server according to the routing policy.
- Increased Security: A Nginx reverse proxy also acts as a line of defense for your backend servers. Configuring a reverse proxy ensures that the identity of your backend servers remains unknown.
- Better Performance: Nginx has been known to perform better in delivering static content file and analyse URLs
- Easy Logging and Auditing: Since there is only one single point of access when a Nginx reverse proxy is implemented, this makes logging and auditing much simpler.
- Encrypted Connection By encrypting the connection between the client and the Nginx reverse Proxy with TLS, users profit from a encrypted and securized HTTPS connection, protecting their data.
Requirements:
- You have an account and are logged into console.scaleway.com
- You have configured your SSH Key
- You have sudo privileges or access to the root user.
- You have an web application running on a non-standard web port on the instance
- You have a compute instance running Ubuntu Bionic Beaver
- Make sure your domain name points towards your server ip (A or AAAA record)
Installing and Configuring Nginx
Note: This tutorial requires that you have already a web application running on your instance. You can for example install a lightweight web server like Webfsd, which runs on port 8000 by default to be joignable on the standard HTTP(s) ports via the proxy. If required it can be installed with apt install webfs
In the following example, we will configure an Nginx reverse proxy in front of an Apache web server. As a result, we assume that Apache is already installed and configured (on the same machine).
1 . Update the APT packet cache and install the Nginx web server via the packet manger:
2 . Disable the default virtual host, that is pre-configured when Nginx is istalled via Ubuntu's packet manager apt:
3 . Enter the directory /etc/nginx/sites-available and create a reverse proxy configuration file.
4 . Paste the following Nginx configuration in the text editor. The proxy server redirects all incomming connections on port 80 to the Webfsd server, listening on port 8000. Edit the port value depending on the applications specific port.
Note: Accesses and errors are located in a log files at /var/log/nginx.
5 . Copy the configuration from /etc/nginx/sites-available to /etc/nginx/sites-enabled. It is recommended to use a symbolic link.
6 . Test the Nginx configuration file
which returns
7 . Open a web browser on your local computer and paste your public_ip which will display your web applications homepage.
Adding TLS to your Nginx Reverse Proxy using Let's Encrypt
Multiple Proxy Manager Job
Important: Make sure your domain name points towards your server ip (A or AAAA record).
With the current setup, all incoming traffic on the standard, non-securized, HTTP port is anserwered by Nginx, which passes it to the web application on the instance.
For security reasons, it is recommended to add an encryption layer with TLS/SSL and to use HTTPS. Whilst it is technically possible to use self-signed certficates, it may cause very inconveniences as a warning is displayed by default in an users web browser when a self-signed certificate is used. A certificate authentity (CA) can issue trusted certificates which a recognized by most modern web browsers. The CA Let's Encrypt provides TLS certificate for free and the configuration of Nginx can be done easily with Certbot, a tool provided by the EFF.
1 . Install Certbot on your instance by using the APT packet manager:
2 . Certbot provides a plugin designed for the Nginx web server, automatizing most of the configuration work related with requesting, installing and managing the TLS certificate:
3 . Answer the prompts that display on the screen to request a valid Let's Encrypt TLS certificate:
When asked if you want to redirect HTTP traffic automatically to HTTPS, choose the option 2. This enables the automatic redirection of all incoming requests via an unencrypted HTTP connection to a secure HTTPS connection. Providing an additional layer of security for the Web application running behind the Nginx reverse proxy.
