I am not sure if this is a package specific issue or an upstream issue, however, it has come to my attention that when WAN IP is not present and a frontend has been configured, HAProxy instead of waiting for the WAN IP, it tries to bind to all interfaces (0.0.0.0) which results in HAProxy crashing since webui is already using port 80 on local interfaces.
I have noticed this issue while my ISP was working on the lines.
I am not sure if this is a package specific issue or an upstream issue, however, it has come to my attention that when WAN IP is not present and a frontend has been configured, HAProxy instead of waiting for the WAN IP, it tries to bind to all interfaces (0.0.0.0) which results in HAProxy crashing since webui is already using port 80 on local interfaces.
I have noticed this issue while my ISP was working on the lines.
haproxy-devel 0.63_3 pfsense plus 24.03
More details about the issue can be found at https://forum.netgate.com/topic/190033/pfsense-webconfigurator-is-binding-wan-ip-port-80-and-stopping-haproxy