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 5 months ago.
Updated about 2 months ago.
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
- 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.
- Status changed from New to Feedback
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.
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.
- Status changed from Feedback to Duplicate
- Is duplicate of Bug #16618: Forcing a service restart of HAProxy does not affect backend servers added
Also available in: Atom
PDF