{"id":5128,"date":"2020-03-06T21:37:23","date_gmt":"2020-03-06T18:37:23","guid":{"rendered":"https:\/\/kifarunix.com\/?p=5128"},"modified":"2020-03-12T21:07:28","modified_gmt":"2020-03-12T18:07:28","slug":"install-and-setup-haproxy-on-centos-8","status":"publish","type":"post","link":"https:\/\/kifarunix.com\/install-and-setup-haproxy-on-centos-8\/","title":{"rendered":"Install and Setup HAProxy on CentOS 8"},"content":{"rendered":"\n<p>This guide will walk you through how to install and setup HAProxy on CentOS 8. <a rel=\"noreferrer noopener\" aria-label=\"HAProxy (opens in a new tab)\" href=\"https:\/\/www.haproxy.org\/\" target=\"_blank\">HAProxy<\/a> is the current de-facto standard opensource load balancer. It offers high availability,&nbsp;load balancing and proxying for TCP and HTTP-based applications.<\/p>\n\n\n\n<p>While offering load balancing, HAProxy supports different algorithms for load balancing. Some of the commonly used ones include;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>Roundrobin<\/strong>&nbsp;\u2013 This is the default algorithm and it enables HAProxy to select each server to serve requests in turns according to their weights.<\/li><li><strong>leastconn<\/strong>&nbsp;\u2013 The server with the lowest number of connections receives the connections. It is recommended where very long sessions are expected, such as LDAP, SQL.<\/li><li><strong>source<\/strong>&nbsp;\u2013 With this algorithm, 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 ensures that the same client IP address will always reach the same server as long as no server goes down or up. If the hash result changes due to the number of running servers changing, many clients will be directed to a different server.<\/li><\/ul>\n\n\n\n<p>Read more on HAProxy load balancing algorithms on the&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/www.haproxy.org\/download\/2.1\/doc\/configuration.txt\" target=\"_blank\">documentation page<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Install and Setup HAProxy on CentOS 8<\/h2>\n\n\n\n<p>For the purposes of demonstrating how HAProxy basically operates, this guide uses uses three virtual machines; one running as HAProxy load balancer and two others running web servers serving basic html pages.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Install HAProxy on CentOS 8<\/h3>\n\n\n\n<p>Run system update.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>dnf update<\/code><\/pre>\n\n\n\n<p>After the system update is done, you can proceed to install HAProxy. HAProxy is available on the default CentOS 8 repos and the installation is as simple as running the command;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>dnf install haproxy<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Configuring HAProxy on&nbsp;CentOS 8<\/h3>\n\n\n\n<p><strong><code>\/etc\/haproxy\/haproxy.cfg<\/code><\/strong> is the default HAProxy configuration file. Below is a sample HAProxy default configuration file with no comments;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>grep -v \"^ *#\" \/etc\/haproxy\/haproxy.cfg | grep -v \"^$\"<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>global\n    log         127.0.0.1 local2\n    chroot      \/var\/lib\/haproxy\n    pidfile     \/var\/run\/haproxy.pid\n    maxconn     4000\n    user        haproxy\n    group       haproxy\n    daemon\n    stats socket \/var\/lib\/haproxy\/stats\n    ssl-default-bind-ciphers PROFILE=SYSTEM\n    ssl-default-server-ciphers PROFILE=SYSTEM\ndefaults\n    mode                    http\n    log                     global\n    option                  httplog\n    option                  dontlognull\n    option http-server-close\n    option forwardfor       except 127.0.0.0\/8\n    option                  redispatch\n    retries                 3\n    timeout http-request    10s\n    timeout queue           1m\n    timeout connect         10s\n    timeout client          1m\n    timeout server          1m\n    timeout http-keep-alive 10s\n    timeout check           10s\n    maxconn                 3000\nfrontend main\n    bind *:5000\n    acl url_static       path_beg       -i \/static \/images \/javascript \/stylesheets\n    acl url_static       path_end       -i .jpg .gif .png .css .js\n    use_backend static          if url_static\n    default_backend             app\nbackend static\n    balance     roundrobin\n    server      static 127.0.0.1:4331 check\nbackend app\n    balance     roundrobin\n    server  app1 127.0.0.1:5001 check\n    server  app2 127.0.0.1:5002 check\n    server  app3 127.0.0.1:5003 check\n    server  app4 127.0.0.1:5004 check<\/code><\/pre>\n\n\n\n<p>As you can see on the above configuration file, there are four HAProxy configuration sections;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>The&nbsp;<em><code>global<\/code><\/em>&nbsp;settings which defines the parameters that apply to all servers running HAProxy<\/li><li>The&nbsp;<em><code>default<\/code><\/em>&nbsp;settings section defines the parameters that apply to all proxy subsections in a configuration (<em><code>frontend<\/code><\/em>,&nbsp;<em><code>backend<\/code><\/em>, and&nbsp;<em><code>listen<\/code><\/em>).<\/li><li>The&nbsp;<em><code>frontend<\/code><\/em>&nbsp;settings section defines the servers&#8217; listening sockets for client connection requests.&nbsp;<\/li><li>The&nbsp;<em><code>backend<\/code><\/em>&nbsp;settings section defines the real server IP addresses as well as the load balancer scheduling algorithm.<\/li><li>Sometimes, both <code>backend<\/code> and <code>frontend<\/code> can be combined under the <code>listen<\/code> section.<\/li><\/ul>\n\n\n\n<p>Read more about these sections on <a rel=\"noreferrer noopener\" aria-label=\"HAProxy essential sections (opens in a new tab)\" href=\"https:\/\/www.haproxy.com\/blog\/the-four-essential-sections-of-an-haproxy-configuration\/\" target=\"_blank\">HAProxy essential sections<\/a>.<\/p>\n\n\n\n<p>Create a backup of the HAProxy configuration file.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>cp \/etc\/haproxy\/haproxy.cfg{,.old}<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Defining Global HAProxy Settings<\/h4>\n\n\n\n<p>In our configuration, we will leave the default global settings as it.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>global\n    log         127.0.0.1 local2\n    chroot      \/var\/lib\/haproxy\n    pidfile     \/var\/run\/haproxy.pid\n    maxconn     4000\n    user        haproxy\n    group       haproxy\n    daemon\n    stats socket \/var\/lib\/haproxy\/stats\n    ssl-default-bind-ciphers PROFILE=SYSTEM\n    ssl-default-server-ciphers PROFILE=SYSTEM<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Define HAProxy Default Settings<\/h4>\n\n\n\n<p>We will leave the default settings as is;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>defaults\n    mode                    http\n    log                     global\n    option                  httplog\n    option                  dontlognull\n    option http-server-close\n    option forwardfor       except 127.0.0.0\/8\n    option                  redispatch\n    retries                 3\n    timeout http-request    10s\n    timeout queue           1m\n    timeout connect         10s\n    timeout client          1m\n    timeout server          1m\n    timeout http-keep-alive 10s\n    timeout check           10s\n    maxconn                 3000<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Defining HAProxy Frontend Settings<\/h4>\n\n\n\n<p>In this section, we will define how HAProxy is externally accessed to enable access to the backend servers. Since most options have been defined on defaults settings section, here is our frontend settings;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>frontend lb01\n    bind 192.168.56.133:80\n    default_backend kifaruapps<\/code><\/pre>\n\n\n\n<p>Where;<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>bind<\/strong>&nbsp;defines an given IP address and port on which HAProxy listens on.<\/li><li><code><strong>default_backend<\/strong><\/code>&nbsp;gives the name of a&nbsp;<code>backend<\/code>&nbsp;to send traffic to.<\/li><\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Defining HAProxy Backend Settings<\/h4>\n\n\n\n<p>On Backend section, define the real backend server IP addresses as well as the load balancer scheduling algorithm.&nbsp;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>backend kifaruapps\n    balance roundrobin\n    server webapp01  192.168.2.112:8080 check\n    server webapp02  192.168.58.9:80 check<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>balance<\/strong>&nbsp;setting defines the roundrobin load balancer scheduling algorithm.<\/li><li><strong>server<\/strong>&nbsp;setting specify the servers available in the back end.<\/li><li><strong>check<\/strong>&nbsp;\u2013 enables health checks on the server. By default, a server is always considered available. If set, the server is available when accepting periodic TCP connections, to ensure that it is really able to serve requests.<\/li><\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Define HAProxy Listen Settings<\/h4>\n\n\n\n<p>You can optionally add the listen section to enable HAProxy statistics. HAProxy provides a dashboard called the <strong>HAProxy Stats page<\/strong> that displays the metrics related to the health of your servers, current request rates, response times, and more that gives a granular data on a per-frontend, backend, and server basis.<\/p>\n\n\n\n<p>The Stats page can be enabled as shown below;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>listen stats\n    bind  192.168.56.133:8088       # Bind stats to port 8088\n    log   global                    # Enable Logging\n    stats enable                    # enable statistics reports \n    stats hide-version              # Hide the version of HAProxy\n    stats refresh 30s               # HAProxy refresh time\n    stats show-node                 # Shows the hostname of the node\n    stats auth lbadmin:P@ssword     # Authentication for Stats page\n    stats uri \/lb_stats             # Statistics URL<\/code><\/pre>\n\n\n\n<p>Ensure that the stats port is allowed on firewall.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>firewall-cmd --add-port=8088\/tcp --permanent<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>firewall-cmd --reload<\/code><\/pre>\n\n\n\n<p>Be sure to check SELinux logs just in case anything is not accessible.<\/p>\n\n\n\n<p>Finally, this is how our HAProxy configuration file is like;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>global\n    log         127.0.0.1 local2\n    chroot      \/var\/lib\/haproxy\n    pidfile     \/var\/run\/haproxy.pid\n    maxconn     4000\n    user        haproxy\n    group       haproxy\n    daemon\n    stats socket \/var\/lib\/haproxy\/stats\n    ssl-default-bind-ciphers PROFILE=SYSTEM\n    ssl-default-server-ciphers PROFILE=SYSTEM\ndefaults\n    mode                    http\n    log                     global\n    option                  httplog\n    option                  dontlognull\n    option http-server-close\n    option forwardfor       except 127.0.0.0\/8\n    option                  redispatch\n    retries                 3\n    timeout http-request    10s\n    timeout queue           1m\n    timeout connect         10s\n    timeout client          1m\n    timeout server          1m\n    timeout http-keep-alive 10s\n    timeout check           10s\n    maxconn                 3000\nfrontend lb01\n    bind 192.168.56.133:80\n    default_backend kifarunixapps    \nbackend kifarunixapps\n    balance     roundrobin\n    server webapp01  192.168.2.112:8080 check\n    server webapp02  192.168.58.9:80 check\nlisten stats\n    bind  192.168.56.133:8088       # Bind stats to port 8088\n    stats enable                    # enable statistics reports  \n    stats hide-version              # Hide the version of HAProxy\n    stats refresh 30s               # HAProxy refresh time\n    stats show-node                 # Shows the hostname of the node\n    stats auth lbadmin:P@ssword     # Authentication for Stats page\n    stats uri \/lb_stats             # Statistics URL<\/code><\/pre>\n\n\n\n<p>Read more about the configuration options on HAProxy&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/cbonte.github.io\/haproxy-dconv\/2.0\/intro.html\" target=\"_blank\">documentation page<\/a>.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Verify HAProxy Configuration<\/h4>\n\n\n\n<p>To check HAProxy config file for any syntax errors, run the command below;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>haproxy -c -f \/etc\/haproxy\/haproxy.cfg<\/code><\/pre>\n\n\n\n<p>If all is well, you should get such an output;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>Configuration file is valid<\/code><\/pre>\n\n\n\n<p>Open HAProxy port on firewall.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>firewall-cmd --add-port=80\/tcp --permanent\nfirewall-cmd --reload<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Running HAProxy on CentOS 8<\/h4>\n\n\n\n<p>To start and enable HAProxy to run on system boot, run the command below;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>systemctl enable --now haproxy<\/code><\/pre>\n\n\n\n<p>Check the status of HAProxy.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>systemctl status haproxy<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>\u25cf haproxy.service - HAProxy Load Balancer\n   Loaded: loaded (\/usr\/lib\/systemd\/system\/haproxy.service; enabled; vendor preset: disabled)\n   Active: active (running) since Thu 2020-03-05 22:34:58 EAT; 2s ago\n  Process: 3262 ExecStartPre=\/usr\/sbin\/haproxy -f $CONFIG -c -q (code=exited, status=0\/SUCCESS)\n Main PID: 3263 (haproxy)\n    Tasks: 2 (limit: 5047)\n   Memory: 2.5M\n   CGroup: \/system.slice\/haproxy.service\n           \u251c\u25003263 \/usr\/sbin\/haproxy -Ws -f \/etc\/haproxy\/haproxy.cfg -p \/run\/haproxy.pid\n           \u2514\u25003265 \/usr\/sbin\/haproxy -Ws -f \/etc\/haproxy\/haproxy.cfg -p \/run\/haproxy.pid\n\nMar 05 22:34:58 ceph-admin.kifarunix-demo.com systemd[1]: Starting HAProxy Load Balancer...\nMar 05 22:34:58 ceph-admin.kifarunix-demo.com systemd[1]: Started HAProxy Load Balancer.<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Configure HAProxy Logging on CentOS 8<\/h3>\n\n\n\n<p>To configure HAProxy standard logging edit&nbsp;<strong>\/etc\/rsyslog.conf<\/strong>&nbsp;and enable UDP syslog reception on port 514 by removing comments (<strong>#<\/strong>) on the lines,&nbsp;<strong>#module(load=\u201dimudp\u201d)<\/strong>&nbsp;and&nbsp;<strong>#input(type=\u201dimudp\u201d port=\u201d514\u2033)<\/strong>&nbsp;as shown below.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>vim \/etc\/rsyslog.conf<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>...\n# Provides UDP syslog reception\n# for parameters see http:\/\/www.rsyslog.com\/doc\/imudp.html\n<strong>module(load=\"imudp\")<\/strong> # needs to be done just once\n<strong>input(type=\"imudp\" port=\"514\")\n<\/strong>...<\/code><\/pre>\n\n\n\n<p>Next, disable logging of private authentication messages sent to&nbsp;<strong>local2<\/strong>&nbsp;facility, (<strong>local2.none<\/strong>) on&nbsp;<strong>\/var\/log\/messages<\/strong>&nbsp;and enable logging on&nbsp;<strong>\/var\/log\/haproxy.log<\/strong>&nbsp;as shown below.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>...\n*.info;mail.none;authpriv.none;cron.none,<strong>local2.none<\/strong>                \/var\/log\/messages\nlocal2.* \/var\/log\/haproxy.log<\/code><\/pre>\n\n\n\n<p>Save the configuration file and run the command below to check for any errors.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>rsyslogd -N1<\/code><\/pre>\n\n\n\n<p>Next, restart Rsyslog and HAProxy<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>systemctl restart rsyslog haproxy<\/code><\/pre>\n\n\n\n<p>You should now be able to have HAProxy logs on <code>\/var\/log\/haproxy.log<\/code>.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>tail -f \/var\/log\/haproxy.log<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Configure Apache X-Forwarded-For Logging on Backend Servers<\/h3>\n\n\n\n<p>Since we have configured HAProxy to add HTTP header \u201cX-Forwarded-For\u201d to all requests sent to the backend server (<strong>option forwardfor<\/strong>), you can configure logging for the same on the backend server. This ensures the IP address of the requesting client is captured instead of the HAProxy load balancer.<\/p>\n\n\n\n<p>Therefore, login to the backend servers and configure Apache to log X-Forwarded-For headers. The default line we are changing is;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>...\n<code>LogFormat \"%h %l %u %t \\\"%r\\\" %&gt;s %b \\\"%{Referer}i\\\" \\\"%{User-Agent}i\\\"\" combined<\/code>\n<code>LogFormat \"%h %l %u %t \\\"%r\\\" %&gt;s %b\" common<\/code>\n...<\/code><\/pre>\n\n\n\n<p>Hence, edit this line such that it looks like;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>...\n<strong>LogFormat \"\\\"%{X-Forwarded-For}i\\\" %l %u %t \\\"%r\\\" %&gt;s %b \\\"%{Referer}i\\\" \\\"%{User-Agent}i\\\"\" combined<\/strong>\nLogFormat \"%h %l %u %t \\\"%r\\\" %&gt;s %b\" common\n...<\/code><\/pre>\n\n\n\n<p>Save the file and run Apache configuration file syntax check command.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>apachectl configtest<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>Syntax OK<\/code><\/pre>\n\n\n\n<p>Restart Apache<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>systemctl restart httpd<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Testing HAProxy Load Balancer on CentOS 8<\/h2>\n\n\n\n<p>To verify that HAProxy is able to load balance the http requests, navigate to browser and access HAProxy using either the hostname or IP address.<\/p>\n\n\n\n<p>Since it is using the <strong><code>roundrobin<\/code><\/strong> algorithm, when you refresh the page, you should be able to get content from both backend servers served.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"690\" height=\"193\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2020\/03\/webapp01.png\" alt=\"\" class=\"wp-image-5139\" title=\"\"><\/figure>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"707\" height=\"201\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2020\/03\/webapp02.png\" alt=\"\" class=\"wp-image-5140\" title=\"\"><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Checking HAProxy Statistics<\/h2>\n\n\n\n<p>To check the statistics of your frontend and backend servers, simply navigate to stats url defined on the listen section; <strong>http:\/\/server-IP_OR_hostname:8088\/lb_stats<\/strong>. Set the appropriate URL.<\/p>\n\n\n\n<p>When prompted, authentication using the credentials defined by the <code>stats auth<\/code> on the <strong>listen section<\/strong>, in this demo, lbadmin:P@ssword, for username and password.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"920\" height=\"326\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2020\/03\/haproxy-auth.png\" alt=\"\" class=\"wp-image-5143\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2020\/03\/haproxy-auth.png?v=1583520111 920w, https:\/\/kifarunix.com\/wp-content\/uploads\/2020\/03\/haproxy-auth-768x272.png?v=1583520111 768w\" sizes=\"(max-width: 920px) 100vw, 920px\" \/><\/figure>\n\n\n\n<p>HAProxy statistics<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1358\" height=\"488\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2020\/03\/haproxy-stats.png\" alt=\"Install and Setup HAProxy on CentOS 8\" class=\"wp-image-5144\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2020\/03\/haproxy-stats.png?v=1583520141 1358w, https:\/\/kifarunix.com\/wp-content\/uploads\/2020\/03\/haproxy-stats-768x276.png?v=1583520141 768w\" sizes=\"(max-width: 1358px) 100vw, 1358px\" \/><\/figure>\n\n\n\n<p>That marks the end of our guide on how to install and setup HAProxy on CentOS 8.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Related Tutorials<\/h3>\n\n\n\n<p><a rel=\"noreferrer noopener\" aria-label=\" (opens in a new tab)\" href=\"https:\/\/kifarunix.com\/setup-haproxy-load-balancer-on-fedora-30-fedora-29\/\" target=\"_blank\">Setup HAProxy Load Balancer on Fedora 30\/Fedora 29<\/a><\/p>\n\n\n\n<p><a href=\"https:\/\/kifarunix.com\/configure-haproxy-with-ssl-on-ubuntu-18-04-debian-10-9\/\">Configure HAP<\/a><a rel=\"noreferrer noopener\" aria-label=\"r (opens in a new tab)\" href=\"https:\/\/kifarunix.com\/configure-haproxy-with-ssl-on-ubuntu-18-04-debian-10-9\/\" target=\"_blank\">r<\/a><a href=\"https:\/\/kifarunix.com\/configure-haproxy-with-ssl-on-ubuntu-18-04-debian-10-9\/\">oxy Load Balancer with SSL on Ubuntu 18.04\/Debian 10\/9<\/a><\/p>\n\n\n\n<p><a href=\"https:\/\/kifarunix.com\/how-to-install-and-configure-pound-apache-load-balancer-on-ubuntu-16-04\/\" target=\"_blank\" rel=\"noreferrer noopener\" aria-label=\" (opens in a new tab)\">How to Install and Configure Pound as Apache HTTP Load balancer on Ubuntu 16.04<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>This guide will walk you through how to install and setup HAProxy on CentOS 8. HAProxy is the current de-facto standard opensource load balancer. It<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_lock_modified_date":false,"footnotes":""},"categories":[1032,121,92],"tags":[1317,1142,1033,1316,1315,95],"class_list":["post-5128","post","type-post","status-publish","format-standard","hentry","category-haproxy","category-howtos","category-load-balancers","tag-apache-load-balancer","tag-centos-8","tag-haproxy","tag-haproxy-apache-centos-8","tag-haproxy-centos-8","tag-load-balancer","generate-columns","tablet-grid-50","mobile-grid-100","grid-parent","grid-50"],"_links":{"self":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/5128"}],"collection":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/comments?post=5128"}],"version-history":[{"count":10,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/5128\/revisions"}],"predecessor-version":[{"id":5200,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/5128\/revisions\/5200"}],"wp:attachment":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media?parent=5128"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/categories?post=5128"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/tags?post=5128"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}