@dr1m
Running on memory here.. afaik haproxy is 'subscribed' to carp events, and as such should be able to start soon after becoming master..
https://github.com/pfsense/FreeBSD-ports/blob/084b4ad9f65198720720f84d04eeed7c441ed49c/net/pfSense-pkg-haproxy/files/usr/local/pkg/haproxy.xml#L52

dont have time to check why that might fail now.. way past bedtime already here..

As for having haproxy run on both nodes, there isn't much of a downside besides that 'healthchecks' will be fired from both haproxy instances and might increase the load of the webserver a little bit..

@johnpoz
yup, i had the default 2048, bumped to 4096

Redmine issue created:
https://redmine.pfsense.org/issues/11680

Please elaborate.
Noone would be able to help if the problem isn't well described.

@piba

Thanx for the help man!

Now, yesterday I have already tested a bit with a backend and frontend, but I ran into problems...I will create a new issue to explain what I want to achieve and what errors I ran into

(whithout above settings and rules, I guess beside safety this doesn't affect the workability of ACME/HAproxy ?)

@vito
So what did you configure to attempt to get to above goal?

@orionis Any feedback?

@simbad please create a bugreport https://docs.netgate.com/pfsense/en/latest/development/bug-reports.html

Squid version in pfSense 2.5/21.02 is 4.13:

[2.5.0-RELEASE][root@xxx]/root: pkg info squid squid-4.13 Name : squid Version : 4.13

please test and leave your comment on https://redmine.pfsense.org/issues/10608

Anyone have any ideas?