Installation

Install HAProxy Enterprise on Azure

In this section, you will learn how to install HAProxy Enterprise on Azure.

Get support Jump to heading

To get the most out of HAProxy Enterprise in Azure, activate support.

You need to activate support to get access to some parts of the documentation, such as WAF.

Contact us:

Info Details
Email contact@haproxy.com
Hours of operation 4am - 6pm EST/EDT
Target response time for critical issues 8 hours

If you require 24x7 support, significantly shorter SLAs, and consultative support, please activate your support account. Visit the Azure Support Activation page to sign up for a login to the customer portal.

For support terms and related information, see HAProxy Legal Policies.

Launch HAProxy Enterprise Jump to heading

To launch HAProxy Enterprise directly from the Azure Marketplace:

  1. From the Azure Marketplace, search for HAProxy Enterprise and choose one of the virtual machine images from the list that have the HAProxy Technologies logo. Options include an Ubuntu Server edition and a Red Hat Enterprise Linux edition.

    Choose a machine image

  2. On the details page, click Get It Now and then select the software plan, which is the version of HAProxy Enterprise that you want to install.

    Choose a software plan

  3. On the next screen, click Create to launch the virtual machine. You can also click Start with a pre-set configuration to set up the VM with CPU and memory-optimized for a common workload.

  4. On the Create a virtual machine screen, fill in the fields for the resource group, virtual machine name, region, availability zone, image size, and Administrator account. We recommend setting up an SSH keypair here so that you can access your machine using SSH.

    Create the VM

  5. Continue through to the Networking screen. Choose whether you want to assign a public IP address to the load balancer.

    • You can give the virtual machine a public IP, which makes it accessible from the Internet.
    • Or, you can set the Public IP field to None and select under Load balancing, Place this virtual machine behind an existing load-balancing solution, which allows you to place two or more HAProxy Enterprise servers behind an Azure Load Balancer. This allows you to run your HAProxy Enterprise load balancers in an active-active setup for high availability. You must create the Azure Load Balancer before you can complete this step.
  6. Continue through the other tabs until you reach the Review + Create screen. Click Create to create the virtual machine.

Connect to the HAProxy Enterprise instance Jump to heading

During installation, you had the option to configure an SSH keypair that you can use to connect to the virtual machine.

  1. If necessary, change the permissions on the private key file that you downloaded:

    nix
    chmod 600 my-haproxy-enterprise_key.pem
    nix
    chmod 600 my-haproxy-enterprise_key.pem
  2. Copy the public IPv4 address for the instance from the Azure portal.

  3. Connect to the HAProxy Enterprise instance through its public IP using SSH. For example:

    nix
    ssh -i my-haproxy-enterprise_key.pem azureuser@20.80.234.150
    nix
    ssh -i my-haproxy-enterprise_key.pem azureuser@20.80.234.150

    If you set up an Azure Load Balancer in front of your instance, then you will need to go to the Load balancers screen and create an inbound NAT rule that maps a port for SSH (e.g. 222) on the Azure Load Balancer to port 22 on the HAProxy Enterprise instance.

Manage the HAProxy Enterprise service Jump to heading

The HAProxy Enterprise service runs at startup. You can manage the process with systemctl.

For example, use systemctl status to check that the service is running:

nix
sudo systemctl status hapee-<VERSION>-lb
nix
sudo systemctl status hapee-<VERSION>-lb
output
text
hapee-VERSION-lb.service - HAPEE Load Balancer
Loaded: loaded (/lib/systemd/system/hapee-VERSION-lb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/hapee-VERSION-lb.service.d
└─override.conf
Active: active (running) since Tue 2021-03-30 15:47:08 UTC; 47min ago
Main PID: 983 (hapee-lb)
Tasks: 3 (limit: 4615)
Memory: 12.2M
CGroup: /system.slice/hapee-VERSION-lb.service
├─983 /opt/hapee-VERSION/sbin/hapee-lb -Ws -f /etc/hapee-VERSION/hapee-lb.cfg -p /run/hapee-VERSION-lb.pid -m 2623 -f /etc/hapee-VERSION/dashboard-module.cfg
└─993 /opt/hapee-VERSION/sbin/hapee-lb -Ws -f /etc/hapee-VERSION/hapee-lb.cfg -p /run/hapee-VERSION-lb.pid -m 2623 -f /etc/hapee-VERSION/dashboard-module.cfg
output
text
hapee-VERSION-lb.service - HAPEE Load Balancer
Loaded: loaded (/lib/systemd/system/hapee-VERSION-lb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/hapee-VERSION-lb.service.d
└─override.conf
Active: active (running) since Tue 2021-03-30 15:47:08 UTC; 47min ago
Main PID: 983 (hapee-lb)
Tasks: 3 (limit: 4615)
Memory: 12.2M
CGroup: /system.slice/hapee-VERSION-lb.service
├─983 /opt/hapee-VERSION/sbin/hapee-lb -Ws -f /etc/hapee-VERSION/hapee-lb.cfg -p /run/hapee-VERSION-lb.pid -m 2623 -f /etc/hapee-VERSION/dashboard-module.cfg
└─993 /opt/hapee-VERSION/sbin/hapee-lb -Ws -f /etc/hapee-VERSION/hapee-lb.cfg -p /run/hapee-VERSION-lb.pid -m 2623 -f /etc/hapee-VERSION/dashboard-module.cfg

Access the Real-time Dashboard Jump to heading

Deprecation notice

The Real-time Dashboard has been marked as deprecated and is scheduled for removal. HAProxy Enterprise 2.8 will be the last version to support it.

  1. Display the HAProxy Enterprise Real-time Dashboard credentials, which are stored in the file /README.txt. For example:

    nix
    sudo cat /README.txt
    nix
    sudo cat /README.txt
    output
    text
    username: dashboard
    password: 091l/Bw2
    output
    text
    username: dashboard
    password: 091l/Bw2
  2. Connect to the dashboard through either HTTP (port 9022) or HTTPS (port 9023). The URLs are http://<Public IPv4 address>:9022/ and https://<Public IPv4 address>:9023/.

    Real-time Dashboard

    Connecting to http://<Public IPv4 address> displays the load balancer’s statistics.

Do you have any suggestions on how we can improve the content of this page?