-
Notifications
You must be signed in to change notification settings - Fork 647
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
net/haproxy: help with ACL/Action configuration #264
Comments
|
Hi @Julien-nl, HAProxy is a complex beast, so you'll need to add some configuration to make this work: (assuming that you have already setup frontends/backends) You need to add
You need
And you need
To actually use the newly created
(Note that you're free to change the FYI, we're aware that the current ACL/Action UI can be quite confusing, especially for users that are not too familiar with HAProxy's internals. We're working on an improvement that will be available in one of the next releases (#208). |
No ETA, sorry. (The new release will make things a little less confusing, but it would not solve your configuration error.)
If I understand you correctly, your previous configuration was a NAT Port Forward to forward HTTPS traffic from OPNsense to your internal servers. If you want to use HAProxy instead, you need to disable these NAT Port Forward rules, yes. Otherwise HAProxy would never receive the traffic.
You need to use an IP address that is locally configured on OPNsense, otherwise HAProxy fails to start. Most likely you want to use the same IP address that you were using as "source address" in your NAT rule. |
I am not sure I can follow you here. what do you mean use IP locally configure on OPNsense? which IP need to use ? Thank you |
You need to hit the TAB key after entering the IP:PORT information. (opnsense/core#1689)
It does not make sense to me to keep using a port forward.
I can't answer this question without knowing your setup. I'm guessing that the services that you have mentioned ("dns1.domain.com" and "dns2.domain.com") currently point to an official IP address that is configured on OPNsense (WAN interface?). If this is the case, use this WAN IP address as listen address for your HAProxy frontend. |
You haven't posted any error message. Please use the |
|
Please use the |
That's really odd. Please try from the OPNsense console (choose option 12 from the console menu or connect through SSH): And paste the output here. |
|
thank you for your continue support fraenki, in the mean while I have the NAT on, turning the services on, do.i have to turn the NAT first off? or having the NAT on doesn't affect the service to start ? thank you |
|
Dear fraenki , |
HAProxy clearly states that there is an error in a rule. Please check the "Actions" in the GUI, they seem to be invalid/incomplete.
NAT does not affect service start/restart. FWIW, we will release HAProxy plugin version 2.0 within the next two weeks (#330). It provides a new GUI and I hope it helps you to find the error in your configuration. |
|
I'm closing this issue, because I think it's a misconfiguration and not a bug.
Please add a link to your forum thread here. Thanks! |













Hi guys,
lately we have moved from pfsense to opnsense.
we have installed haproxy but I can't get it to work to get https forwarded to 3 different host o the lan.
front and back end are created I just need to know which the option to use Compose expression
we have dns1.domain.com and dns2.domain.com
dns1.domain.com forward to 10.10.10.10
and dns2.domain.com forward to 10.10.10.11
over https
hope someone can help me get this working
thank you
The text was updated successfully, but these errors were encountered: