Upgrade

Upgrade HAProxy Enterprise on Linux

On this page

Using HAProxy Fusion?

If you’re using HAProxy Fusion, then see the HAProxy Fusion - Nodes topic instead.

To upgrade to a new, major version of HAProxy Enterprise from an older version, please use the Upgrade procedure. However, if you want to install the latest patches for your current version without upgrading to a new, major version, please use the Update procedure.

Upgrade Jump to heading

You can upgrade HAProxy Enterprise on the following operating systems:

HAProxy Enterprise version Release date End of life Supported OS (architecture)
3.1r1 Feb 2025 Feb 2026
  • AlmaLinux 8 (x86_64)
    AlmaLinux 9 (x86_64)
  • Debian 11 (amd64)
    Debian 12 (amd64)
  • RHEL 8 (x86_64)
    RHEL 9 (x86_64)
  • Rocky Linux 8 (x86_64)
    Rocky Linux 9 (x86_64)
  • Oracle 8 (x86_64)
    Oracle 9 (x86_64)
  • SUSE 15.6 (x86_64)
  • Ubuntu 22.04 (amd64, arm64)
    Ubuntu 24.04 (amd64, arm64)

The upgrade procedure installs a new major version of HAProxy Enterprise.

  1. Issues with the HAProxy Enterprise configuration can cause the load balancer to fail after an upgrade. Even if the service is performing as desired before the upgrade, the upgrade could introduce changes that cause a failure afterward.

    Validate the HAProxy Enterprise configuration file before proceeding with the upgrade.

    Use the hapee-lb command with the -c option to validate configuration files.

    Depending on your version, the command’s output indicates that the file is valid in these ways:

    • In version 2.8 and earlier, the command indicates a valid configuration by printing Configuration file is valid in addition to setting the zero return status.
    • In version 2.9 and later, the command sets the zero return status for a valid configuration but does not display a message. To display the message, include the -V option on the command line.

    Multiple configuration files

    If you have multiple configuration files in your application, be sure to check them all in the correct order.

    Validate the configuration file as follows:

    Validate the configuration file
    nix
    sudo /opt/hapee-3.1/sbin/hapee-lb -c -f /etc/hapee-3.1/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-3.1/sbin/hapee-lb -c -f /etc/hapee-3.1/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-3.1/sbin/hapee-lb -c -f /etc/hapee-3.1/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-3.1/sbin/hapee-lb -c -f /etc/hapee-3.1/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-3.0/sbin/hapee-lb -c -f /etc/hapee-3.0/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-3.0/sbin/hapee-lb -c -f /etc/hapee-3.0/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-3.0/sbin/hapee-lb -c -f /etc/hapee-3.0/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-3.0/sbin/hapee-lb -c -f /etc/hapee-3.0/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-2.8/sbin/hapee-lb -c -f /etc/hapee-2.8/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-2.8/sbin/hapee-lb -c -f /etc/hapee-2.8/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-2.8/sbin/hapee-lb -c -f /etc/hapee-2.8/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-2.8/sbin/hapee-lb -c -f /etc/hapee-2.8/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-2.6/sbin/hapee-lb -c -f /etc/hapee-2.6/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-2.6/sbin/hapee-lb -c -f /etc/hapee-2.6/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-2.6/sbin/hapee-lb -c -f /etc/hapee-2.6/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-2.6/sbin/hapee-lb -c -f /etc/hapee-2.6/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-2.4/sbin/hapee-lb -c -f /etc/hapee-2.4/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-2.4/sbin/hapee-lb -c -f /etc/hapee-2.4/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-2.4/sbin/hapee-lb -c -f /etc/hapee-2.4/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-2.4/sbin/hapee-lb -c -f /etc/hapee-2.4/hapee-lb.cfg -V

    Alerts and warnings that appear in the console output explain the errors encountered. An alert is a fatal condition and prohibits the service from starting. A warning indicates a condition that is not fatal now but may become fatal in the target release. Address all the errors until you receive the successful output: Configuration file is valid.

  2. If the HAProxy Enterprise server is part of a high-availability cluster, take it out of the cluster:

    • If using Active/Active clustering, update your network to stop sending traffic to the load balancer. For example, if using DNS roundrobin, remove the load balancer from DNS.
    • If using Active/Standby clustering, then on the active load balancer edit /etc/hapee-extras/hapee-vrrp.cfg. Lower the priority value to less than the standby load balancer’s priority. This will put the active load balancer into the standby state and simultaneously activate the standby load balancer. Then restart the hapee-extras-vrrp or hapee-extras-vrrp22 service.

  3. Install HAProxy Enterprise by running the following command, specifying the desired version with --version, and replacing <HAProxy Enterprise Key> with your HAProxy Enterprise license key.

    Install the software
    nix
    wget https://www.haproxy.com/static/install_haproxy_enterprise.sh
    sudo bash ./install_haproxy_enterprise.sh \
      --version 3.1r1 \
      --key <HAProxy Enterprise key>
    nix
    wget https://www.haproxy.com/static/install_haproxy_enterprise.sh
    sudo bash ./install_haproxy_enterprise.sh \
      --version 3.1r1 \
      --key <HAProxy Enterprise key>
    nix
    wget https://www.haproxy.com/static/install_haproxy_enterprise.sh
    sudo bash ./install_haproxy_enterprise.sh \
      --version 3.0r1 \
      --key <HAProxy Enterprise key>
    nix
    wget https://www.haproxy.com/static/install_haproxy_enterprise.sh
    sudo bash ./install_haproxy_enterprise.sh \
      --version 3.0r1 \
      --key <HAProxy Enterprise key>
    nix
    wget https://www.haproxy.com/static/install_haproxy_enterprise.sh
    sudo bash ./install_haproxy_enterprise.sh \
      --version 2.8r1 \
      --key <HAProxy Enterprise key>
    nix
    wget https://www.haproxy.com/static/install_haproxy_enterprise.sh
    sudo bash ./install_haproxy_enterprise.sh \
      --version 2.8r1 \
      --key <HAProxy Enterprise key>
    nix
    wget https://www.haproxy.com/static/install_haproxy_enterprise.sh
    sudo bash ./install_haproxy_enterprise.sh \
      --version 2.6r1 \
      --key <HAProxy Enterprise key>
    nix
    wget https://www.haproxy.com/static/install_haproxy_enterprise.sh
    sudo bash ./install_haproxy_enterprise.sh \
      --version 2.6r1 \
      --key <HAProxy Enterprise key>
    nix
    wget https://www.haproxy.com/static/install_haproxy_enterprise.sh
    sudo bash ./install_haproxy_enterprise.sh \
      --version 2.4r1 \
      --key <HAProxy Enterprise key>
    nix
    wget https://www.haproxy.com/static/install_haproxy_enterprise.sh
    sudo bash ./install_haproxy_enterprise.sh \
      --version 2.4r1 \
      --key <HAProxy Enterprise key>

  4. Reinstall additional modules: you may be running additional modules with HAProxy Enterprise, which you must also reinstall when you upgrade to a new release. Install a package using its name, for example:

    Example Install a module
    nix
    sudo apt-get install hapee-3.1r1-lb-update
    nix
    sudo apt-get install hapee-3.1r1-lb-update
    nix
    sudo yum install hapee-3.1r1-lb-update
    nix
    sudo yum install hapee-3.1r1-lb-update
    nix
    sudo zypper install hapee-3.1r1-lb-update
    nix
    sudo zypper install hapee-3.1r1-lb-update
    nix
    sudo pkg install hapee-3.1r1-lb-update
    nix
    sudo pkg install hapee-3.1r1-lb-update
    nix
    sudo apt-get install hapee-3.0r1-lb-update
    nix
    sudo apt-get install hapee-3.0r1-lb-update
    nix
    sudo yum install hapee-3.0r1-lb-update
    nix
    sudo yum install hapee-3.0r1-lb-update
    nix
    sudo zypper install hapee-3.0r1-lb-update
    nix
    sudo zypper install hapee-3.0r1-lb-update
    nix
    sudo pkg install hapee-3.0r1-lb-update
    nix
    sudo pkg install hapee-3.0r1-lb-update
    nix
    sudo apt-get install hapee-2.8r1-lb-update
    nix
    sudo apt-get install hapee-2.8r1-lb-update
    nix
    sudo yum install hapee-2.8r1-lb-update
    nix
    sudo yum install hapee-2.8r1-lb-update
    nix
    sudo zypper install hapee-2.8r1-lb-update
    nix
    sudo zypper install hapee-2.8r1-lb-update
    nix
    sudo pkg install hapee-2.8r1-lb-update
    nix
    sudo pkg install hapee-2.8r1-lb-update
    nix
    sudo apt-get install hapee-2.6r1-lb-update
    nix
    sudo apt-get install hapee-2.6r1-lb-update
    nix
    sudo yum install hapee-2.6r1-lb-update
    nix
    sudo yum install hapee-2.6r1-lb-update
    nix
    sudo zypper install hapee-2.6r1-lb-update
    nix
    sudo zypper install hapee-2.6r1-lb-update
    nix
    sudo pkg install hapee-2.6r1-lb-update
    nix
    sudo pkg install hapee-2.6r1-lb-update
    nix
    sudo apt-get install hapee-2.4r1-lb-update
    nix
    sudo apt-get install hapee-2.4r1-lb-update
    nix
    sudo yum install hapee-2.4r1-lb-update
    nix
    sudo yum install hapee-2.4r1-lb-update
    nix
    sudo zypper install hapee-2.4r1-lb-update
    nix
    sudo zypper install hapee-2.4r1-lb-update
    nix
    sudo pkg install hapee-2.4r1-lb-update
    nix
    sudo pkg install hapee-2.4r1-lb-update

  5. Copy the configuration files from your existing instance to your new instance. In addition to the configuration files, copy any associated files such as maps, certificates, and so on. The default configuration file is located here.

    Configuration file location
    text
    /etc/hapee-3.1/hapee-lb.cfg
    text
    /etc/hapee-3.1/hapee-lb.cfg
    text
    /etc/hapee-3.0/hapee-lb.cfg
    text
    /etc/hapee-3.0/hapee-lb.cfg
    text
    /etc/hapee-2.8/hapee-lb.cfg
    text
    /etc/hapee-2.8/hapee-lb.cfg
    text
    /etc/hapee-2.6/hapee-lb.cfg
    text
    /etc/hapee-2.6/hapee-lb.cfg
    text
    /etc/hapee-2.4/hapee-lb.cfg
    text
    /etc/hapee-2.4/hapee-lb.cfg

  6. Validate your HAProxy Enterprise configuration file against the new version of HAProxy Enterprise.

    Use the hapee-lb command with the -c option to validate configuration files.

    Depending on your version, the command’s output indicates that the file is valid in these ways:

    • In version 2.8 and earlier, the command indicates a valid configuration by printing Configuration file is valid in addition to setting the zero return status.
    • In version 2.9 and later, the command sets the zero return status for a valid configuration but does not display a message. To display the message, include the -V option on the command line.

    Multiple configuration files

    If you have multiple configuration files in your application, be sure to check them all in the correct order.

    Validate the configuration file as follows:

    Validate the configuration file
    nix
    sudo /opt/hapee-3.1/sbin/hapee-lb -c -f /etc/hapee-3.1/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-3.1/sbin/hapee-lb -c -f /etc/hapee-3.1/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-3.1/sbin/hapee-lb -c -f /etc/hapee-3.1/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-3.1/sbin/hapee-lb -c -f /etc/hapee-3.1/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-3.0/sbin/hapee-lb -c -f /etc/hapee-3.0/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-3.0/sbin/hapee-lb -c -f /etc/hapee-3.0/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-3.0/sbin/hapee-lb -c -f /etc/hapee-3.0/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-3.0/sbin/hapee-lb -c -f /etc/hapee-3.0/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-2.8/sbin/hapee-lb -c -f /etc/hapee-2.8/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-2.8/sbin/hapee-lb -c -f /etc/hapee-2.8/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-2.8/sbin/hapee-lb -c -f /etc/hapee-2.8/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-2.8/sbin/hapee-lb -c -f /etc/hapee-2.8/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-2.6/sbin/hapee-lb -c -f /etc/hapee-2.6/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-2.6/sbin/hapee-lb -c -f /etc/hapee-2.6/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-2.6/sbin/hapee-lb -c -f /etc/hapee-2.6/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-2.6/sbin/hapee-lb -c -f /etc/hapee-2.6/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-2.4/sbin/hapee-lb -c -f /etc/hapee-2.4/hapee-lb.cfg -V
    nix
    sudo /opt/hapee-2.4/sbin/hapee-lb -c -f /etc/hapee-2.4/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-2.4/sbin/hapee-lb -c -f /etc/hapee-2.4/hapee-lb.cfg -V
    nix
    sudo docker exec hapee /opt/hapee-2.4/sbin/hapee-lb -c -f /etc/hapee-2.4/hapee-lb.cfg -V

    Alerts and warnings that appear in the console output explain the errors encountered. An alert is a fatal condition and prohibits the service from starting. A warning indicates a condition that is not fatal now but may become fatal in the target release. Address all the errors until you receive the successful output: Configuration file is valid.

  7. Disable the old HAProxy Enterprise service from starting with the system, and enable the new version.

    Disable old service
    nix
    sudo systemctl disable hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl enable hapee-3.1r1-lb
    nix
    sudo systemctl disable hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl enable hapee-3.1r1-lb
    nix
    sudo systemctl disable hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl enable hapee-3.0r1-lb
    nix
    sudo systemctl disable hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl enable hapee-3.0r1-lb
    nix
    sudo systemctl disable hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl enable hapee-2.8r1-lb
    nix
    sudo systemctl disable hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl enable hapee-2.8r1-lb
    nix
    sudo systemctl disable hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl enable hapee-2.6r1-lb
    nix
    sudo systemctl disable hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl enable hapee-2.6r1-lb
    nix
    sudo systemctl disable hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl enable hapee-2.4r1-lb
    nix
    sudo systemctl disable hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl enable hapee-2.4r1-lb

  8. Stop the old HAProxy Enterprise service, and start the new service.

    Stop old service
    nix
    sudo systemctl stop hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl start hapee-3.1r1-lb
    nix
    sudo systemctl stop hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl start hapee-3.1r1-lb
    nix
    sudo systemctl stop hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl start hapee-3.0r1-lb
    nix
    sudo systemctl stop hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl start hapee-3.0r1-lb
    nix
    sudo systemctl stop hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl start hapee-2.8r1-lb
    nix
    sudo systemctl stop hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl start hapee-2.8r1-lb
    nix
    sudo systemctl stop hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl start hapee-2.6r1-lb
    nix
    sudo systemctl stop hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl start hapee-2.6r1-lb
    nix
    sudo systemctl stop hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl start hapee-2.4r1-lb
    nix
    sudo systemctl stop hapee-<PREVIOUS_VERSION>-lb
    sudo systemctl start hapee-2.4r1-lb

  9. Run tail -f /var/log/syslog (or distribution equivalent) to check for warnings or errors.

  10. Run curl localhost to ensure that HAProxy Enterprise is responding. Adjust address/port as needed, and use a local address that is currently active on the box and not a VRRP IP.

  11. Put the upgraded server back into the cluster.

  12. Repeat this procedure on secondary load balancers after restoring the current load balancer to active service.

Post-upgrade Jump to heading

After you upgrade, see the section on enterprise modules on how to enable and configure each one.

After the new HAProxy Enterprise version has been running for a while, you can uninstall the old HAProxy Enterprise version. To uninstall the old version:

Uninstall old version
nix
sudo apt purge hapee-3.1r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-3.1r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-3.1r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-3.1r1-\*
sudo systemctl restart rsyslog
nix
sudo rm -i `rpm -q --configfiles hapee-3.1r1-lb`
sudo yum remove hapee-3.1r1-\*
sudo systemctl restart rsyslog
nix
sudo rm -i `rpm -q --configfiles hapee-3.1r1-lb`
sudo yum remove hapee-3.1r1-\*
sudo systemctl restart rsyslog
nix
sudo zypper remove hapee-3.1r1-\*
sudo systemctl restart rsyslog
nix
sudo zypper remove hapee-3.1r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-3.0r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-3.0r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-3.0r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-3.0r1-\*
sudo systemctl restart rsyslog
nix
sudo rm -i `rpm -q --configfiles hapee-3.0r1-lb`
sudo yum remove hapee-3.0r1-\*
sudo systemctl restart rsyslog
nix
sudo rm -i `rpm -q --configfiles hapee-3.0r1-lb`
sudo yum remove hapee-3.0r1-\*
sudo systemctl restart rsyslog
nix
sudo zypper remove hapee-3.0r1-\*
sudo systemctl restart rsyslog
nix
sudo zypper remove hapee-3.0r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-2.8r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-2.8r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-2.8r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-2.8r1-\*
sudo systemctl restart rsyslog
nix
sudo rm -i `rpm -q --configfiles hapee-2.8r1-lb`
sudo yum remove hapee-2.8r1-\*
sudo systemctl restart rsyslog
nix
sudo rm -i `rpm -q --configfiles hapee-2.8r1-lb`
sudo yum remove hapee-2.8r1-\*
sudo systemctl restart rsyslog
nix
sudo zypper remove hapee-2.8r1-\*
sudo systemctl restart rsyslog
nix
sudo zypper remove hapee-2.8r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-2.6r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-2.6r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-2.6r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-2.6r1-\*
sudo systemctl restart rsyslog
nix
sudo rm -i `rpm -q --configfiles hapee-2.6r1-lb`
sudo yum remove hapee-2.6r1-\*
sudo systemctl restart rsyslog
nix
sudo rm -i `rpm -q --configfiles hapee-2.6r1-lb`
sudo yum remove hapee-2.6r1-\*
sudo systemctl restart rsyslog
nix
sudo zypper remove hapee-2.6r1-\*
sudo systemctl restart rsyslog
nix
sudo zypper remove hapee-2.6r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-2.4r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-2.4r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-2.4r1-\*
sudo systemctl restart rsyslog
nix
sudo apt purge hapee-2.4r1-\*
sudo systemctl restart rsyslog
nix
sudo rm -i `rpm -q --configfiles hapee-2.4r1-lb`
sudo yum remove hapee-2.4r1-\*
sudo systemctl restart rsyslog
nix
sudo rm -i `rpm -q --configfiles hapee-2.4r1-lb`
sudo yum remove hapee-2.4r1-\*
sudo systemctl restart rsyslog
nix
sudo zypper remove hapee-2.4r1-\*
sudo systemctl restart rsyslog
nix
sudo zypper remove hapee-2.4r1-\*
sudo systemctl restart rsyslog

Update Jump to heading

The update procedure installs the latest build for your current HAProxy Enterprise version in order to benefit from the latest bug fixes.

  1. Optional: Save the current load balancer configuration as a backup.

    Backup configuration
    nix
    sudo cp /etc/hapee-3.1/hapee-lb.cfg /etc/hapee-3.1/hapee-lb.cfg.current
    nix
    sudo cp /etc/hapee-3.1/hapee-lb.cfg /etc/hapee-3.1/hapee-lb.cfg.current
    nix
    sudo cp /etc/hapee-3.0/hapee-lb.cfg /etc/hapee-3.0/hapee-lb.cfg.current
    nix
    sudo cp /etc/hapee-3.0/hapee-lb.cfg /etc/hapee-3.0/hapee-lb.cfg.current
    nix
    sudo cp /etc/hapee-2.8/hapee-lb.cfg /etc/hapee-2.8/hapee-lb.cfg.current
    nix
    sudo cp /etc/hapee-2.8/hapee-lb.cfg /etc/hapee-2.8/hapee-lb.cfg.current
    nix
    sudo cp /etc/hapee-2.6/hapee-lb.cfg /etc/hapee-2.6/hapee-lb.cfg.current
    nix
    sudo cp /etc/hapee-2.6/hapee-lb.cfg /etc/hapee-2.6/hapee-lb.cfg.current
    nix
    sudo cp /etc/hapee-2.4/hapee-lb.cfg /etc/hapee-2.4/hapee-lb.cfg.current
    nix
    sudo cp /etc/hapee-2.4/hapee-lb.cfg /etc/hapee-2.4/hapee-lb.cfg.current

  2. Optional: Simulate the package upgrade to check for potential errors:

    nix
    sudo apt update
    sudo apt upgrade --simulate
    nix
    sudo apt update
    sudo apt upgrade --simulate
    nix
    sudo apt update
    sudo apt upgrade --simulate
    nix
    sudo apt update
    sudo apt upgrade --simulate
    nix
    sudo yum check-update
    nix
    sudo yum check-update
    nix
    sudo zypper update --dry-run
    nix
    sudo zypper update --dry-run

    Search the output for hapee, which will show the new package version. If there are no errors, perform the upgrade.

  3. Upgrade the packages on your system. Note that a prompt may display asking whether the system can restart service automatically during the upgrade. To avoid any disruption to service, you can uncheck HAProxy Enterprise from this list and then manually execute sudo systemctl reload hapee-<VERSION>-lb, which will not drop traffic.

    nix
    sudo apt update
    sudo apt upgrade
    nix
    sudo apt update
    sudo apt upgrade
    nix
    sudo apt update
    sudo apt upgrade
    nix
    sudo apt update
    sudo apt upgrade
    nix
    sudo yum update
    nix
    sudo yum update
    nix
    sudo zypper update
    nix
    sudo zypper update

  4. Reload the HAProxy Enterprise service to start the new version.

    Reload service
    nix
    sudo systemctl reload hapee-3.1-lb
    nix
    sudo systemctl reload hapee-3.1-lb
    nix
    sudo systemctl reload hapee-3.0-lb
    nix
    sudo systemctl reload hapee-3.0-lb
    nix
    sudo systemctl reload hapee-2.8-lb
    nix
    sudo systemctl reload hapee-2.8-lb
    nix
    sudo systemctl reload hapee-2.6-lb
    nix
    sudo systemctl reload hapee-2.6-lb
    nix
    sudo systemctl reload hapee-2.4-lb
    nix
    sudo systemctl reload hapee-2.4-lb

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

Previous page Docker Next page Administration
© 2025 HAProxy Technologies, LLC. All Rights Reserved
Manage Cookie Preferences