Project

General

Profile

Actions

Bug #16544

closed

During WAN failover event, HAproxy frontend IPs are not transferred from the primary to the secondary pfSense HAproxy service

Added by Lauren C 4 months ago. Updated about 1 month ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
HAProxy
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.9.x
Affected Plus Version:
25.07.1
Affected Architecture:
1537

Description

Configuration synchronization via XMLRPC is enabled. Configuration appears to be syncing, but failover of the frontend LAN IPs does not occur when the primary pfSense firewall goes offline. Secondary always shows an error pertaining to multiple frontends using the same undefined IP, and HAproxy does not function when the secondary is the active firewall. This causes a production outage.


Files

Screenshot 2025-11-17 at 11.20.01.png (61.6 KB) Screenshot 2025-11-17 at 11.20.01.png sync enabled Lauren C, 11/17/2025 04:28 PM
primary.png (294 KB) primary.png primary frontends Lauren C, 11/17/2025 04:28 PM
secondary.png (673 KB) secondary.png secondary frontends with perpetual error Lauren C, 11/17/2025 04:28 PM

Related issues

Is duplicate of Bug #16618: Forcing a service restart of HAProxy does not affect backend serversResolvedMarcos M

Actions
Actions #1

Updated by Marcos M 4 months ago

  • Priority changed from Very High to Normal

Try testing on the 25.11-BETA if possible. I'm not able to reproduce it there which indicates it was likely fixed by related changes present in the 25.11 version.

Actions #2

Updated by Marcos M 4 months ago

  • Status changed from New to Feedback
Actions #3

Updated by Lauren C 4 months ago

Unfortunately I cannot run beta software as this is for a production environment. It seems it'll be in my company's best interest to move to HAproxy on a standalone pair of systems for future stability, so will be taking that route.

Actions #4

Updated by Kris Phillips 3 months ago

Lauren C wrote in #note-3:

Unfortunately I cannot run beta software as this is for a production environment. It seems it'll be in my company's best interest to move to HAproxy on a standalone pair of systems for future stability, so will be taking that route.

Hello,

25.11 is now in stable. Let us know if you can still reproduce this issue on the latest stable build.

Actions #5

Updated by Marcos M about 1 month ago

  • Status changed from Feedback to Duplicate
Actions #6

Updated by Marcos M about 1 month ago

  • Is duplicate of Bug #16618: Forcing a service restart of HAProxy does not affect backend servers added
Actions

Also available in: Atom PDF