Bug #8760
closed
Port Forwarding Rules Stop Working when HAProxy is Configured/Running
Added by Acat L over 6 years ago.
Updated over 6 years ago.
Affected Architecture:
amd64
Description
HAProxy version: 1.7.11
pfSense version: 2.4.3-RELEASE-p1 (amd64)
built on Thu May 10 15:02:52 CDT 2018
FreeBSD 11.1-RELEASE-p10
I have Port Forward rules that are tested and running. When HAProxy is used (i.e. configured with FE/BE), all Port Forward rules stop working. All configured ports of the Port Forward rules stops working. It will only work again when HAProxy package is uninstalled.
HAProxy version: 1.7.11
pfSense version: 2.4.3-RELEASE-p1 (amd64)
built on Thu May 10 15:02:52 CDT 2018
FreeBSD 11.1-RELEASE-p10
I have Port Forward rules that are tested and running. When HAProxy is started (i.e. after configuration FE/BE), all Port Forward rules stop working. All configured ports of the Port Forward rules stops working even within shell. It will only work again when HAProxy package is uninstalled.
- Status changed from New to Rejected
- Priority changed from High to Normal
Not enough information here. Many, many people are successfully using haproxy and port forwards (including me). It's unlikely to be a problem exactly as stated. Please post on the forum or pfSense subreddit to discuss the issue and track down the actual underlying cause.
I've been able to reproduce it 5x already. It specifically occurs when a new BE is created.
My setup has 2 test NATs (forwards to 80/443 on 1 host on the LAN zone). They're perfectly working fine. HAProxy also starts up fine when no BE/FE configured. Everything is in default. But when a new BE is configured which points to the same 1 host:port on the LAN zone, NAT rules stop working.
Issue doesn't happen on my production setup with haproxy 1.7.4 on pfsense 2.3.4-Release-p1.
Also available in: Atom
PDF
Updated by 
Updated by