How to configure load balancing using Nginx

Advantages of load balancing

Load balancing is an excellent way to scale out your application and increase its performance and redundancy. Nginx, a popular web server software, can be configured as a simple yet powerful load balancer to improve your server’s resource availability and efficiency.

How does Nginx work? Nginx creates a single entry point for a distributed web application that works on multiple servers.

This guide describes the advantages of load balancing. Learn how to set up load balancing with nginx for your cloud servers.

As a prerequisite, you’ll need to have at least two hosts with web server software installed and configured to see the benefit of the load balancer. If you already have one web host set up, duplicate it by creating a custom image and deploying it onto a new server at your UpCloud Control Panel.

Installing nginx

The first thing to do is set up a new host to serve as your load balancer. Deploy a new instance at your UpCloud Control Panel if you haven’t already. Nginx packages are available in the latest versions of CentOS, Debian, and Ubuntu. So pick whichever of these you prefer.

After setting up the server how you like, install the latest stable nginx. Use one of the following methods.

# Debian and Ubuntu
sudo apt-get update
# Then install the Nginx Open Source edition
sudo apt-get install nginx

# CentOS
# Install the extra packages repository
sudo yum install epel-release
# Update the repositories and install Nginx
sudo yum update
sudo yum install nginx

Once installed, change the directory to the nginx main configuration folder.

cd /etc/nginx/

Depending on your OS, the web server configuration files will be in one of two places.

Ubuntu and Debian follow a rule for storing virtual host files in /etc/nginx/sites-available/, which are enabled through symbolic links to /etc/nginx/sites-enabled/. You can use the command below to enable any new virtual host files.

sudo ln -s /etc/nginx/sites-available/vhost /etc/nginx/sites-enabled/vhost

CentOS users can find their host configuration files under /etc/nginx/conf.d/ in which any .conf type virtual host file gets loaded.

Check that you find at least the default configuration, and then restart nginx.

sudo systemctl restart nginx

Test that the server replies to HTTP requests. Open the load balancer server’s public IP address in your web browser. When you see the default welcoming page for nginx, the installation is successful.

If you have trouble loading the page, check that a firewall is not blocking your connection. For example on CentOS 7 the default firewall rules do not allow HTTP traffic, enable it with the commands below.

sudo firewall-cmd --add-service=http --permanent
sudo firewall-cmd --reload

Then, try reloading your browser.

Configuring nginx as a load balancer

When nginx is installed and tested, start to configure it for load balancing. In essence, all you need to do is set up Nginx with instructions on which type of connections to listen to and where to redirect them. Create a new configuration file using whichever text editor you prefer. For example, with nano:

sudo nano /etc/nginx/conf.d/load-balancer.conf

In the load-balancer.conf, you’ll need to define the following two segments: upstream and server. See the examples below.

# Define which servers to include in the load balancing scheme. 
# It's best to use the servers' private IPs for better performance and security.
# You can find the private IPs at your UpCloud control panel Network section.
http {
   upstream backend {
      server 10.1.0.101; 
      server 10.1.0.102;
      server 10.1.0.103;
   }

   # This server accepts all traffic to port 80 and passes it to the upstream. 
   # Notice that the upstream name and the proxy_pass need to match.

   server {
      listen 80; 

      location / {
          proxy_pass http://backend;
      }
   }
}

Then, save the file and exit the editor.

Next, disable the default server configuration you tested earlier that was working after the installation. Again, this part differs slightly depending on your OS.

On Debian and Ubuntu systems, you’ll need to remove the default symbolic link from the sites-enabled folder.

sudo rm /etc/nginx/sites-enabled/default

CentOS hosts don’t use the same linking. Instead, simply rename the default.conf in the conf.d/ directory to something that doesn’t end with .conf, for example:

sudo mv /etc/nginx/conf.d/default.conf /etc/nginx/conf.d/default.conf.disabled

Then, use the following to restart nginx.

sudo systemctl restart nginx

Check that nginx starts successfully. If the restart fails, take a look at the  /etc/nginx/conf.d/load-balancer.conf you just created to make sure there are no mistypes or missing semicolons.

When you enter the load balancer’s public IP address in your web browser, you should pass it to one of your back-end servers.

Load balancing methods

Load balancing with nginx uses a round-robin algorithm by default if no other method is defined, like in the first example above. With a round-robin scheme, each server is selected in turns according to the order you set them in the load-balancer.conf file. This balances the number of requests equally for short operations.

Least connections-based load balancing is another straightforward method. As the name suggests, this method directs the requests to the server with the least active connections at that time. It works more fairly than round-robin with applications where requests sometimes take longer to complete.

Add the parameter least_conn to your upstream section to enable the least connections balancing method, as shown in the example below.

upstream backend {
   least_conn;
   server 10.1.0.101; 
   server 10.1.0.102;
   server 10.1.0.103;
}

Round-robin and least connections balancing schemes are fair and have their uses. However, they cannot provide session persistence. If your web application requires that the users are subsequently directed to the same back-end server as during their previous connection, use the IP hashing method instead. IP hashing uses the visitor’s IP address to determine which host should be selected to service the request. This allows the visitors to be directed to the same server each time, granted that the server is available and the visitor’s IP address hasn’t changed.

To use this method, add the ip_hash -parameter to your upstream segment, as in the example below.

upstream backend {
   ip_hash;
   server 10.1.0.101; 
   server 10.1.0.102;
   server 10.1.0.103;
}

In a server setup where the available resources between different hosts are unequal, favouring some servers over others might be desirable. Defining server weights allows you to fine-tune the load and further balance it with nginx. The server with the highest weight in the load balancer is selected the most often.

upstream backend {
   server 10.1.0.101 weight=4; 
   server 10.1.0.102 weight=2;
   server 10.1.0.103;
}

For example, in the configuration shown above, the first server is selected twice as often as the second, which again gets twice the requests compared to the third.

Load balancing with HTTPS enabled

Enable HTTPS for your site; it is a great way to protect your visitors and their data. If you haven’t yet implemented encryption on your web hosts, we highly recommend you look at our guide for installing Let’s Encrypt on nginx.

Using encryption with a load balancer is easier than you might think. All you need to do is add another server section to your load balancer configuration file that listens to HTTPS traffic at port 443 with SSL. Then, set up a proxy_pass to your upstream segment, like with the HTTP in the previous example above.

Open your configuration file again for editing.

sudo nano /etc/nginx/conf.d/load-balancer.conf

Then, add the following server segment to the end of the file.

server {
   listen 443 ssl;
   server_name domain_name;
   ssl_certificate /etc/letsencrypt/live/domain_name/cert.pem;
   ssl_certificate_key /etc/letsencrypt/live/domain_name/privkey.pem;
   ssl_protocols TLSv1 TLSv1.1 TLSv1.2;

   location / {
      proxy_pass http://backend;
   }
}

Then, save the file, exit the editor, and restart Nginx.

sudo systemctl restart nginx

Setting up encryption at your load balancer when you are using private network connections to your back end has some great advantages.

• As only your UpCloud servers have access to your private network, you can terminate the SSL at the load balancer and thus only pass forward HTTP connections.
• It also greatly simplifies your certificate management. You can obtain and renew the certificates from a single host.

With the HTTPS-enabled, you can enforce encryption on all connections to your load balancer. Simply update your server segment by listening to port 80 with a server name and a redirection to your HTTPS port. Then, remove or comment out the location portion as it’s no longer needed. See the example below.

server {
   listen 80;
   server_name domain_name;
   return 301 https://$server_name$request_uri;

   #location / {
   #   proxy_pass http://backend;
   #}
}

Save the file again after you have made the changes. Then restart nginx.

sudo systemctl restart nginx

Now, all connections to your load balancer will be served over an encrypted HTTPS connection. Requests to the unencrypted HTTP will be redirected to use HTTPS as well. This provides a seamless transition into encryption. Nothing is required from your visitors.

Health checks

Nginx’s reverse proxy implementations include passive server health checks to determine which servers are available. If a server fails to respond to a request or replies with an error, nginx will note that it has failed and try to avoid forwarding connections to that server for a time.

The number of consecutive unsuccessful connection attempts within a certain time period can be defined in the load balancer configuration file. Set a parameter max_fails to the server lines. By default, when no max_fails is specified, this value is set to 1. Optionally, setting max_fails to 0 will disable health checks for that server.

If max_fails is set to a value greater than 1, subsequent fails must happen within a specific time frame for them to count. This time frame is specified by a parameter, fail_timeout, which also defines how long the server should be considered failed. By default, the fail_timeout is set to 10 seconds.

After a server is marked failed and the time set by fail_timeout has passed, nginx will begin gracefully probing the server with client requests. If the probes return successful, the server is again marked live and included in the load balancing as normal.

upstream backend {
   server 10.1.0.101 weight=5;
   server 10.1.0.102 max_fails=3 fail_timeout=30s;
   server 10.1.0.103;
}

Use the health checks. They allow you to adapt your server back-end to the current demand by powering up or down hosts as required. Adding more servers during high traffic can easily increase your application performance as new resources become automatically available to your load balancer.

Conclusions on the advantages of load balancing

If you wish to improve your web application performance and availability, a load balancer is definitely something to consider. Nginx is powerful yet relatively simple to set up to load balance a web server. Together with an easy encryption solution, such as the Let’s Encrypt client, it makes for a great front-end to your web farm. Check out the documentation for upstream over at nginx.org to learn more.

When you use multiple hosts, the load balancer protects your web service with redundancy, but the load balancer itself can still leave a single point of failure. You can improve high availability by setting up a floating IP between multiple load balancers. Check out our article about floating IPs on UpCloud to learn more.