Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / HAProxy on AlmaLinux 9

HAProxy on AlmaLinux 9 — Support & Quick Start

HAProxy on AlmaLinux 9 — HAProxy on AlmaLinux 9 delivers the de-facto standard open-source load balancer on an enterprise-grade RHEL-compatible base. Published by Derek Coleman & Associates Inc on the Azure Marketplace, deployed in your own Azure subscription.

Email support Product page Azure Marketplace listing

At a glance

Application ports8404 (stats page — the baseline config binds `*:8404`, unauthenticated; the 2026-09-15 image sweep proved it only on 127.0.0.1 from inside the VM. Treat it as loopback-only until you open 8404 in the NSG to your own IP and confirm it answers); 80 and 443 are opened in firewalld but NO frontend listens on them until you add one
Open in browserhttp://127.0.0.1:8404/ from the VM (`curl -sI http://127.0.0.1:8404/`); http://<VM-IP>:8404/ only after you open 8404 in the NSG
Service(s)haproxy
Configuration/etc/haproxy/haproxy.cfg (baseline: a stats frontend only; the AppStream sample is kept at /etc/haproxy/haproxy.cfg.appstream-sample)
Logsjournalctl -u haproxy -f; /var/log/messages (rsyslog local0)
VersionHAProxy (AlmaLinux 9 AppStream package)
PlatformAlmaLinux 9

Quick start

  1. Deploy from the Azure Marketplace (Get It Now → Create), choosing your SSH key at the Administration step.
  2. Allow inbound SSH (22) for yourself plus the application port(s): 8404 (stats) to your IP only, plus 80/443 once you configure frontends — restrict to your own IP where possible. The in-image firewall already allows them; only the Network Security Group (NSG) keeps them closed.
  3. Confirm HAProxy is up from the VM: `curl -sI http://127.0.0.1:8404/` returns 200 (the stats page); to view it in a browser open 8404 in the NSG to your IP only. Then add frontend/backend definitions to /etc/haproxy/haproxy.cfg.
  4. Validate (`haproxy -c -f /etc/haproxy/haproxy.cfg`) and reload (`sudo systemctl reload haproxy`).

First login

  1. No credential is generated. The baseline config serves only the unauthenticated stats page on :8404 — proven on 127.0.0.1:8404 from the VM (2026-09-15 sweep, image 2026.06.26); reaching it from your workstation needs 8404 open in the NSG to your IP only. Add your own frontend/backend sections to /etc/haproxy/haproxy.cfg.
  2. Validate with `haproxy -c -f /etc/haproxy/haproxy.cfg`, then `sudo systemctl reload haproxy`. SELinux: `setsebool -P haproxy_connect_any 1` is already set.

Still stuck?

Email support@dcassociatesgroup.com (response within 1 business day) or send a message via the contact form. Include the offer name, VM size, region, and any log output — sudo journalctl -u <service> -n 100 usually tells the story.