Try this guide out on UpCloud with our free trial! Get started<\/a><\/h3>\n<\/div>\n\n\n\nLoad balancing is a common solution for distributing\u00a0web applications horizontally across multiple hosts while providing the users with a single point of access to the service.\u00a0HAProxy<\/a> is one of the most popular\u00a0open-source load-balancing software, which also offers high availability and proxy functionality.<\/p>\n\n\n\n\nTry UpCloud for free!<\/a><\/div>\n<\/div>\n\n\n\nHAProxy aims to optimise resource usage, maximise throughput, minimise response time, and avoid overloading any single resource. It is available for installation on many Linux distributions like CentOS 8 in this guide, but also on Debian 8<\/a> and Ubuntu 16<\/a> systems.<\/p>\n\n\n\n![\"HAproxy](\"https:\/\/upcloud.com\/media\/haproxy-load-balancer-6.png\")
<\/figure>\n\n\n\nHAProxy is particularly suited for very high-traffic websites and is therefore often used to improve web service reliability and performance for multi-server configurations. This guide lays out the steps for setting up HAProxy as a load balancer on CentOS 8 to its own cloud host which then directs the traffic to your web servers.<\/p>\n\n\n\n
As a pre-requirement for the best results, you should have a minimum of two web servers and a server for the load balancer. The web servers need to be running at least the basic web service such as nginx<\/em> or httpd<\/em> to test out the load balancing between them.<\/p>\n\n\n\nInstalling HAProxy CentOS 8<\/h2>\n\n\n\n
As a fast-developing open-source application HAProxy available for installation in the CentOS default repositories might not be the latest release. To find out what version number is being offered through the official channels enter the following command.<\/p>\n\n\n\n
sudo yum info haproxy<\/pre>\n\n\n\nHAProxy has always three active stable versions of the releases, two of the latest versions in development plus a third older version that is still receiving critical updates. You can always check the currently newest stable version listed on the HAProxy website and then decide which version you wish to go with.<\/p>\n\n\n\n
In this guide, we will be installing the currently latest stable version of 2.0, which was not yet available in the standard repositories. Instead, you will need to install it from the source. But first, check that you have the prerequisites to download and compile the program.<\/p>\n\n\n\n
sudo yum install gcc pcre-devel tar make -y<\/pre>\n\n\n\nDownload the source code with the command below. You can check if there is a newer version available on the HAProxy download page<\/a>.<\/p>\n\n\n\nwget http:\/\/www.haproxy.org\/download\/2.0\/src\/haproxy-2.0.7.tar.gz -O ~\/haproxy.tar.gz<\/pre>\n\n\n\nOnce the download is complete, extract the files using the command below.<\/p>\n\n\n\n
tar xzvf ~\/haproxy.tar.gz -C ~\/<\/pre>\n\n\n\nChange into the extracted source directory.<\/p>\n\n\n\n
cd ~\/haproxy-2.0.7<\/pre>\n\n\n\nThen compile the program for your system.<\/p>\n\n\n\n
make TARGET=linux-glibc<\/pre>\n\n\n\nAnd finally, install HAProxy itself.<\/p>\n\n\n\n
sudo make install<\/pre>\n\n\n\nWith that done, HAProxy is now installed but requires some additional steps to get it operational. Continue below with setting up the software and services.<\/p>\n\n\n\n
Setting up HAProxy for your server<\/h2>\n\n\n\n
Next, add the following directories and the statistics file for HAProxy records.<\/p>\n\n\n\n
sudo mkdir -p \/etc\/haproxy\nsudo mkdir -p \/var\/lib\/haproxy \nsudo touch \/var\/lib\/haproxy\/stats<\/pre>\n\n\n\nCreate a symbolic link for the binary to allow you to run HAProxy commands as a normal user.<\/p>\n\n\n\n
sudo ln -s \/usr\/local\/sbin\/haproxy \/usr\/sbin\/haproxy<\/pre>\n\n\n\nIf you want to add the proxy as a service to the system, copy the haproxy.init<\/tt> file from the examples to your \/etc\/init.d<\/tt> directory. Change the file permissions to make the script executable and then reload the systemd daemon.<\/p>\n\n\n\nsudo cp ~\/haproxy-2.0.7\/examples\/haproxy.init \/etc\/init.d\/haproxy\nsudo chmod 755 \/etc\/init.d\/haproxy\nsudo systemctl daemon-reload<\/pre>\n\n\n\nYou will also need to enable the service to allow it to restart automatically at system boot-up.<\/p>\n\n\n\n
sudo chkconfig haproxy on<\/pre>\n\n\n\nFor general usage, it is also recommended to add a new user for HAProxy to be run under.<\/p>\n\n\n\n
sudo useradd -r haproxy<\/pre>\n\n\n\nAfterwards, you can double-check the installed version number with the following command.<\/p>\n\n\n\n
haproxy -v<\/pre>\n\n\n\nHA-Proxy version 2.0.7 2019\/09\/27 - https:\/\/haproxy.org\/<\/pre>\n\n\n\nIn this case, the version should be 2.0.7 as shown in the example output above.<\/p>\n\n\n\n
Lastly, the firewall on CentOS 8 is quite restrictive for this project by default. Use the following commands to allow the required services and reload the firewall.<\/p>\n\n\n\n
sudo firewall-cmd --permanent --zone=public --add-service=http\nsudo firewall-cmd --permanent --zone=public --add-port=8181\/tcp\nsudo firewall-cmd --reload<\/pre>\n\n\n\nConfiguring the load balancer<\/h2>\n\n\n\n
Setting up an HAProxy load balancer is a quite straightforward process. Basically, all you need to do is tell HAProxy what kind of connections it should be listening for and where the connections should be relayed to.<\/p>\n\n\n\n
This is done by creating a configuration file \/etc\/haproxy\/haproxy.cfg<\/tt> with the defining settings. You can read about the configuration options on the HAProxy documentation page<\/a> if you wish to find out more.<\/p>\n\n\n\nLoad balancing at layer 4<\/h2>\n\n\n\n
Start off with a basic setup. Create a new configuration file, for example, using vi<\/tt> with the command underneath.<\/p>\n\n\n\nsudo vi \/etc\/haproxy\/haproxy.cfg<\/pre>\n\n\n\nAdd the following sections to the file. Replace the server_name<\/tt><\/span> with whatever you want to call your servers on the statistics page and the private_ip<\/tt><\/span> with the private IPs for the servers you wish to direct the web traffic. You can check the private IPs at your UpCloud control panel<\/a> and Private network<\/em> tab under the Network<\/em> menu.<\/p>\n\n\n\nglobal\n log \/dev\/log local0\n log \/dev\/log local1 notice\n chroot \/var\/lib\/haproxy\n stats timeout 30s\n user haproxy\n group haproxy\n daemon\n\ndefaults\n log global\n mode tcp\n option httplog\n option dontlognull\n timeout connect 5000\n timeout client 50000\n timeout server 50000\n\nfrontend http_front\n bind *:80\n stats uri \/haproxy?stats\n default_backend http_back\n\nbackend http_back\n balance roundrobin\n server server_name1<\/span> private_ip1<\/span>:80 check\n server server_name2<\/span> private_ip2<\/span>:80 check<\/pre>\n\n\n\nThis defines a layer 4 load balancer with a front-end name http_front<\/tt> listening to the port number 80<\/tt>, which then directs the traffic to the default backend named http_back<\/tt>. The additional stats URI \/haproxy?stats<\/tt> enables the statistics page at that specified address.<\/p>\n\n\n\nDifferent load balancing algorithms<\/h2>\n\n\n\n
Configuring the servers in the backend section allows HAProxy to use these servers for load balancing according to the roundrobin<\/tt> algorithm whenever available.<\/p>\n\n\n\n
The balancing algorithms are used to decide which server at the backend each connection is transferred to. Some of the useful options include the following:<\/p>\n\n\n\n
\n- Roundrobin: Each server is used in turns according to its weights. This is the smoothest and fairest algorithm when the servers\u2019 processing time remains equally distributed. This algorithm is dynamic, which allows server weights to be adjusted on the fly.<\/li>\n\n\n\n
- Leastconn: The server with the lowest number of connections is chosen. Round-robin is performed between servers with the same load. Using this algorithm is recommended with long sessions, such as LDAP, SQL, TSE, etc, but it is not very well suited for short sessions such as HTTP.<\/li>\n\n\n\n
- First: The first server with available connection slots receives the connection. The servers are chosen from the lowest numeric identifier to the highest, which defaults to the server\u2019s position on the farm. Once a server reaches its maxconn<\/tt> value, the next server is used.<\/li>\n\n\n\n
- Source: The source IP address is hashed and divided by the total weight of the running servers to designate which server will receive the request. This way the same client IP address will always reach the same server while the servers stay the same.<\/li>\n<\/ul>\n\n\n\n
Configuring load balancing for layer 7<\/h2>\n\n\n\n
Another possibility is to configure the load balancer to work on layer 7, which is useful when parts of your web application are located on different hosts. This can be accomplished by conditioning the connection transfer for example by the URL.<\/p>\n\n\n\n
Open the HAProxy configuration file with a text editor.<\/p>\n\n\n\n
sudo vi \/etc\/haproxy\/haproxy.cfg<\/pre>\n\n\n\nThen set the front and backend segments according to the example below.<\/p>\n\n\n\n
defaults\n ...\n mode http<\/span>\n ...\n\nfrontend http_front\n bind *:80\n stats uri \/haproxy?stats\n acl url_blog path_beg \/blog\n use_backend blog_back if url_blog\n default_backend http_back\n\nbackend http_back\n balance roundrobin\n server server_name1<\/span> private_ip1<\/span>:80 check\n server server_name2<\/span> private_ip2<\/span>:80 check\n\nbackend blog_back\n server server_name3<\/span> private_ip3<\/span>:80 check<\/pre>\n\n\n\nThe front end declares an ACL rule named url_blog<\/tt> that applies to all connections with paths that begin with \/blog<\/tt>. Use_backend<\/tt> defines that connections matching the url_blog<\/tt> condition should be served by the backend named blog_back<\/tt>, while all other requests are handled by the default backend.<\/p>\n\n\n\n
On the backend side, the configuration sets up two server groups, http_back<\/tt> like before and the new one called blog_back<\/tt> that servers specifically connections to example.com\/blog<\/tt>.<\/p>\n\n\n\n
After making the configurations, save the file and restart HAProxy with the next command.<\/p>\n\n\n\n
sudo systemctl restart haproxy<\/pre>\n\n\n\nIf you get any errors or warnings at startup, check the configuration for any mistypes and that you have created all the necessary files and folders, then try restarting again.<\/p>\n\n\n\n
Testing the setup<\/h2>\n\n\n\n
With the HAProxy configured and running, open your load balancer server\u2019s public IP in a web browser and check that you get connected to your backend correctly. The parameter stats uri<\/tt> in the configuration enables the statistics page at the defined address.<\/p>\n\n\n\nhttp:\/\/load_balancer_public_ip\/haproxy?stats<\/pre>\n\n\n\nWhen you load the statistics page and all of your servers are listed in green your configuration was successful!<\/p>\n\n\n\n![\"HAProxy](\"https:\/\/upcloud.com\/media\/haproxy-207-2.png\")
<\/figure>\n\n\n\nThe statistics page contains some helpful information to keep track of your web hosts including up and downtimes and session counts. If a server is listed in red, check that the server is powered on and that you can ping it from the load balancer machine.<\/p>\n\n\n\n
In case your load balancer does not reply, check that HTTP connections are not getting blocked by the firewall. Also, confirm that HAProxy is running with the command below.<\/p>\n\n\n\n
sudo systemctl status haproxy<\/pre>\n\n\n\nPassword protecting the statistics page<\/h2>\n\n\n\n
Having the statistics page simply listed at the front end, however, is publicly open for anyone to view, which might not be such a good idea. Instead, you can set it up to its own port number by adding the example below to the end of your haproxy.cfg<\/tt> file. Replace the username<\/tt><\/span> and password<\/tt><\/span> with something secure.<\/p>\n\n\n\nlisten stats\n bind *:8181\n stats enable\n stats uri \/\n stats realm Haproxy Statistics\n stats auth username<\/span>:password<\/span><\/pre>\n\n\n\nAfter adding the new listen<\/tt> group, remove the old reference to the stats uri<\/tt> from the frontend<\/tt> group. When done, save the file and restart HAProxy again.<\/p>\n\n\n\nsudo systemctl restart haproxy<\/pre>\n\n\n\nThen open the load balancer again with the new port number, and log in with the username and password you set in the configuration file.<\/p>\n\n\n\n
http:\/\/load_balancer_public_ip:8181<\/pre>\n\n\n\nCheck that your servers are still reporting all green and then open just the load balancer IP without any port numbers on your web browser.<\/p>\n\n\n\n
http:\/\/load_balancer_public_ip\/<\/pre>\n\n\n\nIf your backend servers have at least slightly different landing pages you will notice that each time you reload the page you get a reply from a different host. You can try out different balancing algorithms in the configuration section or take a look at the full documentation<\/a>.<\/p>\n\n\n\n\nGet started<\/a><\/p>\n<\/div>\n\n\n\nConclusions: HAProxy load balancer<\/h2>\n\n\n\n
Congratulations on successfully configuring the HAProxy load balancer! With a basic load balancer setup, you can considerably increase your web application performance and availability. This guide is however just an introduction to load balancing with HAProxy, which is capable of much more than what could be covered in first-time setup instruction. We recommend experimenting with different configurations with the help of the extensive documentation<\/a> available for HAProxy, and then start planning the load balancing for your production environment.<\/p>\n\n\n\nWhile using multiple hosts to protect your web service with redundancy, the load balancer itself can still leave a single point of failure. You can further improve the high availability by setting up a floating IP between multiple load balancers. You can find out more about this in our article on floating IPs on UpCloud<\/a>.<\/p>\n","protected":false},"featured_media":26929,"comment_status":"open","ping_status":"closed","template":"","community-category":[113,115],"class_list":["post-24603","tutorial","type-tutorial","status-publish","has-post-thumbnail","hentry","community-category-integrations","community-category-load-balancing"],"acf":[],"_links":{"self":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/tutorial\/24603","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/tutorial"}],"about":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/types\/tutorial"}],"replies":[{"embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/comments?post=24603"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/media\/26929"}],"wp:attachment":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/media?parent=24603"}],"wp:term":[{"taxonomy":"community-category","embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/community-category?post=24603"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
HAProxy aims to optimise resource usage, maximise throughput, minimise response time, and avoid overloading any single resource. It is available for installation on many Linux distributions like CentOS 8 in this guide, but also on Debian 8<\/a> and Ubuntu 16<\/a> systems.<\/p>\n\n\n\n HAProxy is particularly suited for very high-traffic websites and is therefore often used to improve web service reliability and performance for multi-server configurations. This guide lays out the steps for setting up HAProxy as a load balancer on CentOS 8 to its own cloud host which then directs the traffic to your web servers.<\/p>\n\n\n\n As a pre-requirement for the best results, you should have a minimum of two web servers and a server for the load balancer. The web servers need to be running at least the basic web service such as nginx<\/em> or httpd<\/em> to test out the load balancing between them.<\/p>\n\n\n\n As a fast-developing open-source application HAProxy available for installation in the CentOS default repositories might not be the latest release. To find out what version number is being offered through the official channels enter the following command.<\/p>\n\n\n\n HAProxy has always three active stable versions of the releases, two of the latest versions in development plus a third older version that is still receiving critical updates. You can always check the currently newest stable version listed on the HAProxy website and then decide which version you wish to go with.<\/p>\n\n\n\n In this guide, we will be installing the currently latest stable version of 2.0, which was not yet available in the standard repositories. Instead, you will need to install it from the source. But first, check that you have the prerequisites to download and compile the program.<\/p>\n\n\n\n Download the source code with the command below. You can check if there is a newer version available on the HAProxy download page<\/a>.<\/p>\n\n\n\n Once the download is complete, extract the files using the command below.<\/p>\n\n\n\n Change into the extracted source directory.<\/p>\n\n\n\n Then compile the program for your system.<\/p>\n\n\n\n And finally, install HAProxy itself.<\/p>\n\n\n\n With that done, HAProxy is now installed but requires some additional steps to get it operational. Continue below with setting up the software and services.<\/p>\n\n\n\n Next, add the following directories and the statistics file for HAProxy records.<\/p>\n\n\n\n Create a symbolic link for the binary to allow you to run HAProxy commands as a normal user.<\/p>\n\n\n\n If you want to add the proxy as a service to the system, copy the haproxy.init<\/tt> file from the examples to your \/etc\/init.d<\/tt> directory. Change the file permissions to make the script executable and then reload the systemd daemon.<\/p>\n\n\n\n You will also need to enable the service to allow it to restart automatically at system boot-up.<\/p>\n\n\n\n For general usage, it is also recommended to add a new user for HAProxy to be run under.<\/p>\n\n\n\n Afterwards, you can double-check the installed version number with the following command.<\/p>\n\n\n\n In this case, the version should be 2.0.7 as shown in the example output above.<\/p>\n\n\n\n Lastly, the firewall on CentOS 8 is quite restrictive for this project by default. Use the following commands to allow the required services and reload the firewall.<\/p>\n\n\n\n Setting up an HAProxy load balancer is a quite straightforward process. Basically, all you need to do is tell HAProxy what kind of connections it should be listening for and where the connections should be relayed to.<\/p>\n\n\n\n This is done by creating a configuration file \/etc\/haproxy\/haproxy.cfg<\/tt> with the defining settings. You can read about the configuration options on the HAProxy documentation page<\/a> if you wish to find out more.<\/p>\n\n\n\n Start off with a basic setup. Create a new configuration file, for example, using vi<\/tt> with the command underneath.<\/p>\n\n\n\n Add the following sections to the file. Replace the server_name<\/tt><\/span> with whatever you want to call your servers on the statistics page and the private_ip<\/tt><\/span> with the private IPs for the servers you wish to direct the web traffic. You can check the private IPs at your UpCloud control panel<\/a> and Private network<\/em> tab under the Network<\/em> menu.<\/p>\n\n\n\n This defines a layer 4 load balancer with a front-end name http_front<\/tt> listening to the port number 80<\/tt>, which then directs the traffic to the default backend named http_back<\/tt>. The additional stats URI \/haproxy?stats<\/tt> enables the statistics page at that specified address.<\/p>\n\n\n\n Configuring the servers in the backend section allows HAProxy to use these servers for load balancing according to the roundrobin<\/tt> algorithm whenever available.<\/p>\n\n\n\n The balancing algorithms are used to decide which server at the backend each connection is transferred to. Some of the useful options include the following:<\/p>\n\n\n\n Another possibility is to configure the load balancer to work on layer 7, which is useful when parts of your web application are located on different hosts. This can be accomplished by conditioning the connection transfer for example by the URL.<\/p>\n\n\n\n Open the HAProxy configuration file with a text editor.<\/p>\n\n\n\n Then set the front and backend segments according to the example below.<\/p>\n\n\n\n The front end declares an ACL rule named url_blog<\/tt> that applies to all connections with paths that begin with \/blog<\/tt>. Use_backend<\/tt> defines that connections matching the url_blog<\/tt> condition should be served by the backend named blog_back<\/tt>, while all other requests are handled by the default backend.<\/p>\n\n\n\n On the backend side, the configuration sets up two server groups, http_back<\/tt> like before and the new one called blog_back<\/tt> that servers specifically connections to example.com\/blog<\/tt>.<\/p>\n\n\n\n After making the configurations, save the file and restart HAProxy with the next command.<\/p>\n\n\n\n If you get any errors or warnings at startup, check the configuration for any mistypes and that you have created all the necessary files and folders, then try restarting again.<\/p>\n\n\n\n With the HAProxy configured and running, open your load balancer server\u2019s public IP in a web browser and check that you get connected to your backend correctly. The parameter stats uri<\/tt> in the configuration enables the statistics page at the defined address.<\/p>\n\n\n\n When you load the statistics page and all of your servers are listed in green your configuration was successful!<\/p>\n\n\n\n The statistics page contains some helpful information to keep track of your web hosts including up and downtimes and session counts. If a server is listed in red, check that the server is powered on and that you can ping it from the load balancer machine.<\/p>\n\n\n\n In case your load balancer does not reply, check that HTTP connections are not getting blocked by the firewall. Also, confirm that HAProxy is running with the command below.<\/p>\n\n\n\n Having the statistics page simply listed at the front end, however, is publicly open for anyone to view, which might not be such a good idea. Instead, you can set it up to its own port number by adding the example below to the end of your haproxy.cfg<\/tt> file. Replace the username<\/tt><\/span> and password<\/tt><\/span> with something secure.<\/p>\n\n\n\n After adding the new listen<\/tt> group, remove the old reference to the stats uri<\/tt> from the frontend<\/tt> group. When done, save the file and restart HAProxy again.<\/p>\n\n\n\n Then open the load balancer again with the new port number, and log in with the username and password you set in the configuration file.<\/p>\n\n\n\n Check that your servers are still reporting all green and then open just the load balancer IP without any port numbers on your web browser.<\/p>\n\n\n\n If your backend servers have at least slightly different landing pages you will notice that each time you reload the page you get a reply from a different host. You can try out different balancing algorithms in the configuration section or take a look at the full documentation<\/a>.<\/p>\n\n\n\n Get started<\/a><\/p>\n<\/div>\n\n\n\n Congratulations on successfully configuring the HAProxy load balancer! With a basic load balancer setup, you can considerably increase your web application performance and availability. This guide is however just an introduction to load balancing with HAProxy, which is capable of much more than what could be covered in first-time setup instruction. We recommend experimenting with different configurations with the help of the extensive documentation<\/a> available for HAProxy, and then start planning the load balancing for your production environment.<\/p>\n\n\n\n While using multiple hosts to protect your web service with redundancy, the load balancer itself can still leave a single point of failure. You can further improve the high availability by setting up a floating IP between multiple load balancers. You can find out more about this in our article on floating IPs on UpCloud<\/a>.<\/p>\n","protected":false},"featured_media":26929,"comment_status":"open","ping_status":"closed","template":"","community-category":[113,115],"class_list":["post-24603","tutorial","type-tutorial","status-publish","has-post-thumbnail","hentry","community-category-integrations","community-category-load-balancing"],"acf":[],"_links":{"self":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/tutorial\/24603","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/tutorial"}],"about":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/types\/tutorial"}],"replies":[{"embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/comments?post=24603"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/media\/26929"}],"wp:attachment":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/media?parent=24603"}],"wp:term":[{"taxonomy":"community-category","embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/community-category?post=24603"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<\/figure>\n\n\n\nInstalling HAProxy CentOS 8<\/h2>\n\n\n\n
sudo yum info haproxy<\/pre>\n\n\n\n
sudo yum install gcc pcre-devel tar make -y<\/pre>\n\n\n\n
wget http:\/\/www.haproxy.org\/download\/2.0\/src\/haproxy-2.0.7.tar.gz -O ~\/haproxy.tar.gz<\/pre>\n\n\n\n
tar xzvf ~\/haproxy.tar.gz -C ~\/<\/pre>\n\n\n\n
cd ~\/haproxy-2.0.7<\/pre>\n\n\n\n
make TARGET=linux-glibc<\/pre>\n\n\n\n
sudo make install<\/pre>\n\n\n\n
Setting up HAProxy for your server<\/h2>\n\n\n\n
sudo mkdir -p \/etc\/haproxy\nsudo mkdir -p \/var\/lib\/haproxy \nsudo touch \/var\/lib\/haproxy\/stats<\/pre>\n\n\n\n
sudo ln -s \/usr\/local\/sbin\/haproxy \/usr\/sbin\/haproxy<\/pre>\n\n\n\n
sudo cp ~\/haproxy-2.0.7\/examples\/haproxy.init \/etc\/init.d\/haproxy\nsudo chmod 755 \/etc\/init.d\/haproxy\nsudo systemctl daemon-reload<\/pre>\n\n\n\n
sudo chkconfig haproxy on<\/pre>\n\n\n\n
sudo useradd -r haproxy<\/pre>\n\n\n\n
haproxy -v<\/pre>\n\n\n\n
HA-Proxy version 2.0.7 2019\/09\/27 - https:\/\/haproxy.org\/<\/pre>\n\n\n\n
sudo firewall-cmd --permanent --zone=public --add-service=http\nsudo firewall-cmd --permanent --zone=public --add-port=8181\/tcp\nsudo firewall-cmd --reload<\/pre>\n\n\n\n
Configuring the load balancer<\/h2>\n\n\n\n
Load balancing at layer 4<\/h2>\n\n\n\n
sudo vi \/etc\/haproxy\/haproxy.cfg<\/pre>\n\n\n\n
global\n log \/dev\/log local0\n log \/dev\/log local1 notice\n chroot \/var\/lib\/haproxy\n stats timeout 30s\n user haproxy\n group haproxy\n daemon\n\ndefaults\n log global\n mode tcp\n option httplog\n option dontlognull\n timeout connect 5000\n timeout client 50000\n timeout server 50000\n\nfrontend http_front\n bind *:80\n stats uri \/haproxy?stats\n default_backend http_back\n\nbackend http_back\n balance roundrobin\n server server_name1<\/span> private_ip1<\/span>:80 check\n server server_name2<\/span> private_ip2<\/span>:80 check<\/pre>\n\n\n\nDifferent load balancing algorithms<\/h2>\n\n\n\n
\n
Configuring load balancing for layer 7<\/h2>\n\n\n\n
sudo vi \/etc\/haproxy\/haproxy.cfg<\/pre>\n\n\n\n
defaults\n ...\n mode http<\/span>\n ...\n\nfrontend http_front\n bind *:80\n stats uri \/haproxy?stats\n acl url_blog path_beg \/blog\n use_backend blog_back if url_blog\n default_backend http_back\n\nbackend http_back\n balance roundrobin\n server server_name1<\/span> private_ip1<\/span>:80 check\n server server_name2<\/span> private_ip2<\/span>:80 check\n\nbackend blog_back\n server server_name3<\/span> private_ip3<\/span>:80 check<\/pre>\n\n\n\nsudo systemctl restart haproxy<\/pre>\n\n\n\n
Testing the setup<\/h2>\n\n\n\n
http:\/\/load_balancer_public_ip\/haproxy?stats<\/pre>\n\n\n\n
<\/figure>\n\n\n\nsudo systemctl status haproxy<\/pre>\n\n\n\n
Password protecting the statistics page<\/h2>\n\n\n\n
listen stats\n bind *:8181\n stats enable\n stats uri \/\n stats realm Haproxy Statistics\n stats auth username<\/span>:password<\/span><\/pre>\n\n\n\nsudo systemctl restart haproxy<\/pre>\n\n\n\n
http:\/\/load_balancer_public_ip:8181<\/pre>\n\n\n\n
http:\/\/load_balancer_public_ip\/<\/pre>\n\n\n\n
Conclusions: HAProxy load balancer<\/h2>\n\n\n\n