My apologies I gave bad advice.

Documentation is opposite what I suggested. https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide-prepare.html#packages

Yes I am using haproxy-devel v0.62_13

That would likely need to be a feature request.

@gamehoundsdev NVM im a idiot, I forgot to disable a 443 mapping on nat ..

@jonathan-young
You can do something like this to insert the /test directory:

In the backend add an ACL:
name: notest
path starts with
"Not" checked
value: /test/

action:
http-request set-path
fmt: /test/%[path]
acl: notest

@ahole4sure no, it is not required if you're using SSL Offloading option on Haproxy frontend. In this case it is better to use http for backend (or issue some internal ssl cert on pfsense for your synology)

@viragomann Oh man! So, I finally figured out the problem. You were correct from the beginning. In fact, nearly every scenario we tried works.

The problem had nothing to do with my setup. My ISP decided to up and block port 80 all of a sudden without telling me. I figured this out by going back to basics. I started up a simple webserver that listened to port 80 and just forwarded directly to that server. Worked on most every other port except 80. Spent 3 hours on the phone with my ISP to get this fixed.

All works now.

I really appreciate the help. I did learn a few things along the way, so not a total waste of time.

Nobody to help with HAProxy?
Thanks

@nasheayahu said in HAProxy - route by domain name:

wwwkohanyimcom Host matches: no no www.kohanyin.com
kohanyimcom Host contains: no no kohanyin.com

I found the problem, my domain was spelled incorrectly... 😧

I added just that one line into the “Global Advanced pass thru” field in the HAproxy Settings tab…applied the configuration changes and it worked immediately. Thanks. How did you do? Many thanks. How can I mark your reply as “solved the problem”!

Edit: The last couple of days I have tried to gather some information of why the service won't start. Unfortunately there is not much information that can help me for specific installations on FreeBSD. But I have tried the following commands, with the output I get. I don't know if someone can see why it fails.

/usr/local/etc/rc.d/haproxy start:
WARNING: failed precmd routine for haproxy
/usr/local/etc/rc.d/haproxy enable:
haproxy enabled in /etc/rc.conf
/usr/local/etc/rc.d/haproxy status:
haproxy is not running.
/usr/local/etc/rc.d/haproxy configtest:
Configuration file has no error but will not start (no listener) => exit(2).
haproxy -f /usr/local/etc/haproxy.conf -p /var/run/haproxy.pid:
[ALERT] 070/102644 (18074) : [haproxy.main()] No enabled listener found (check for 'bind' directives) ! Exiting.

Also, what I've done so far:

Set the protocol for the webConfigurator to https Changed the TCP port to something other than 443 Turned on the Disable webConfigurator redirect rule

Some other information that might be important:

When I click on the (I don't know what else to call it) play button, the gear will load for a few seconds, then reload and then silently fail. Because the Haproxy service isn't enabled, I can't save the change made in settings of; Enable HAProxy.

If anyone has an idea of what might be happening, please let me know because I'm out of idea's.

I was able to solve this by following the HAProxy documentation regarding HTTP to HTTPS redirect.

Adding unless { ssl_fc } to my ACL action on the front end got rid of the error.

Now it looks like : scheme https unless { ssl_fc }

image-01.jpg image-02.jpg

Yeah, you wouldn't want to do that because the backend/frontend need to stay the same protocol.

But if you want to be able to enter fqdn.com and have that redirect to www.fqdn.com/home/somepage.htm you should be able to. And doing it there prevents HAProxy accidentally overmatching.

Steve

Hi @Baker0052 keen to share your haproxy conf. I have the same problem and cannot figure it out.

@viragomann Dachte ich mir schon, ist aber ist trotzdem schade. Irgendwas ist immer, vor allem wenn etwas einfach umzusetzen ist. Das ganze funktioniert ja überraschend gut, nur das die IP-Adressen von der anfragenden Quelle nicht an den HAProxy weitergereicht werden.

@piba see also https://github.com/pfsense/FreeBSD-ports/pull/1066

@piba

So after reading your comment, I installed the devel package and after working out the differences I needed to make that were version related, my OCSP stapling is now working again.

Thanks for the help.

@piba said in 2.4.5_1 PHP Error installing HAProxy:

unset($config['installedpackages']['haproxy']);
write_config("fix haproxy install, remove empty config");
print("config fixed?");

By Jove Sir, I think you got it.

I was able to install HaProxy.

that looks like solution.

Thank you for the quick response

@noplan said in Reverse proxy with HAProxy pointing to the firewall:

@Bob-Dig

Oh yes... I forgot that one

Move to something like 99443
Nothing like 80443 0r 8080

Smashed it out of the park =D thanks for that, needed to do some reading but moving the port seemed to do the trick.

@planetinse
Don't ask, read..
If the certificate is valid for the root domain, then its probably due to the acl's that get added, either check both boxes for checking subject/san, or uncheck them that should allow traffic to pass to the (default) backend. That is assuming you have indeed the same issue, if not, start a different topic please.

@pooperman

there is some issue with SSL handshake:

1.JPG

@PiBa Good news, I got it to work! I did as you suggested and got a self signed certificate on the server using this guide. After that HAProxy is able to route traffic to the host. It even works with the Let's Encrypt wildcard cert I have through the ACME package, so there's no cert errors getting to the site. Thank you for the help again.

@phoadm
Have you configured the haproxy webgui to 'monitor' a carp interface? If so it wont start on that node until that node becomes master.

@lido14
'Normally' IPFW is not running when only pfSense is used without captive-portal..

The quickest fix is probably to give pfSense a reboot.. Haproxy loads and configures IPFW if it 'needs' transparent-client-ip with its current config settings.. If none of the backends require this the IPFW related configuration code is likely completely skipped. It does not remember that it still needs to disable the old ipfw settings.... I guess i need to set a little 'flag' that transparent-client-ip was used and check that to remove the last rules if the current config doesn't use it anymore.. I'm not sure if unloading ipfw itself is possible.. i think there was a issue there...

@crowfather

I get that the backend limit is 1/10th the front end... but still not sure what this resolves.

If you set the front-end to 500 does that mean the back-end is really 500 but is only showing 50. Should we be setting it to 10X the value we want or is it that it only incorrectly displays this way?

--Nikolaos

TLS 1.3 will require OpenSSL 1.1.x, which is only currently available on pfSense 2.5.0 development snapshots. Though it does look like net/haproxy-devel is at 2.0-dev2 on the branch used for pfSense 2.5.0 development, but the pfSense haproxy-devel package doesn't use it (yet).

I'm not aware of any plans to switch that over yet, but it's probably just a matter of time.