I’ve applied an update of the HAPRoxy Package in my pfSense today which raised the HAProxy version from 2.7.6 to 2.8.d6. As soon as the update was done, all tablets in the house and all mobiles lost the connection to HomeAssistant.
Web Browsers are showing the login page, once the credentials are entered the process times out after a while with the error message that no connection to HA can be established.
Login directly to the HA VM via HTTP on the LAN works.
Normally I would blame HAProxy for that, but HomeAssistant is the only application with issues with HAProxy 2.8.
Is there any known workaround for this issue? For now I needed to revert my pfSense back to last nights backup to use my HomeAssistant.
im also running pfsense with haproxy and using acme for lets encrypt certs.
im running a stable version of pfSense CE 2.7.0 and the latest version is 0.63_1 of HAproxy found under package manager.
the installed version of haproxy is “HAProxy version 2.7.8-58c657f, released 2023/05/02”
I just got pfsense install updated a week ago to 2.7.0 as well as update all the packages that is installed on my system. All my backends are working great, no issue and that includes Home Assistant.
maybe your running a development version of pfsense hence your running a bleeding edge version which version 2.8, which is not likely to happen on stable branch.
Indeed I was running the HAproxy-devel package since ages, which updated to HAProxy version 2.8.
I went back to the non-devel for now (and will likely stay with it), but my fear is that this issue will hit us when the regular package is updated to 2.8.x.
You guys are awesome I’ve been banging my head against a wall over this issue and due to my poor timing and other reasons I never tied my haproxy update to the issues. But I feel like I have had the same issue as far as I can tell with all LAN based “trusted login devices” now sat at a login screen. Fingers crossed a fix is found ASAP as its impacting the ‘WAF’
I will continue to check findings etc… but so far this is the only change I can think of since this problem emerged.
Home Assistant: 2023.8.3
pfsensense: 2.7.0-RELEASE
haproxy-2.7.8
the community in pfsense will probably figure something about it if its still a issue, its just that majority of pfsense user dont really run a dev version of the package in production. probably why you dont see something similar issue posted on official forums of pfsense or the subreddit.
who knows, maybe its just a bug that is present with newer dev package that maybe fixed in stable release later on.
