Now you should have pfSense (192.168.3.1) listening on port 443 and HA proxy listening on 192.168.3.30 on port 443 so there won’t be a conflict and it should work how you want. Then change the frontend of HA Proxy to listen on this virtual IP rather than the entire LAN, and finally change pfSense back to port 443. to this IP rather than pfSense (which I believe is 192.168.3.1 in your configuration). Under Firewall - Virtual IPs create a new IP alias, something like 192.168.3.30 (make sure that it’s not in use and outside of your DHCP range etc.) on the LAN interface as a single IP. However, I believe there is a way around this issue. I don’t quite have this config in my lab for other reasons, but I think it should work, and from memory I have tried it in the past, but if I’m wrong, then I apologise in advance for talking nonsense and wasting your time.Īs you have HA Proxy bound to 443 on your LAN you can’t have pfSense also bound to 443, as that would mean two services are using the same IP and the same port, which is not possible, as you’ve found out. I’ve just signed up to (hopefully) fix your issue.
0 kommentar(er)
