<![CDATA[HA Proxy, same server multiple ports (Turnkey Linux)]]>I have a server that's running TurnKey Linux LAMP. IP is 10.20.20.6. It has it's own self sign cert, I want to use mine instead as it's valid.

I can get to https://web.mydomain.net just fine with my cert. However, TKLAMP has some management sites that are accessed by port, Webadmin (12321) and Adminer (12322).

When I go to https://web.mydomain.net:12321 eventually it loads but it's trying to load the self signed and not my cert. See my settings, I'm sure I'm doing something wrong:
backend.png

]]>https://forum.netgate.com/topic/195665/ha-proxy-same-server-multiple-ports-turnkey-linuxRSS for NodeMon, 18 May 2026 04:10:35 GMTWed, 18 Dec 2024 16:38:17 GMT60<![CDATA[Reply to HA Proxy, same server multiple ports (Turnkey Linux) on Wed, 18 Dec 2024 22:19:16 GMT]]>@CreationGuy
That's not a problem. However, you have to configure a separate backend for this. Then you can configure a frontend rule to forward certain traffic to it.

Actually you have all three services within a single backend pool, all in active mode. Hence you cannot determine which per rule.
HAproxy can only load balance between these backens this way.

]]>https://forum.netgate.com/post/1199991https://forum.netgate.com/post/1199991Wed, 18 Dec 2024 22:19:16 GMT<![CDATA[Reply to HA Proxy, same server multiple ports (Turnkey Linux) on Wed, 18 Dec 2024 18:01:02 GMT]]>@viragomann said in HA Proxy, same server multiple ports (Turnkey Linux):

Anyway it doesn't work with all backends in a single backend pool. You have to configure a unique backend for each.

I could use a different host name, however the software is coded to access those sites only via the port.

]]>https://forum.netgate.com/post/1199971https://forum.netgate.com/post/1199971Wed, 18 Dec 2024 18:01:02 GMT<![CDATA[Reply to HA Proxy, same server multiple ports (Turnkey Linux) on Wed, 18 Dec 2024 17:50:49 GMT]]>@CreationGuy said in HA Proxy, same server multiple ports (Turnkey Linux):

When I go to https://web.mydomain.net:12321 eventually it loads but it's trying to load the self signed and not my cert.

So you might have forwarded this port 12321 to the backend.

Anyway it doesn't work with all backends in a single backend pool. You have to configure a unique backend for each.

If you want to access them using the port for whatever reason, you have also add this port to the frontend or configure additional frontends.

The more smart way is to use a different hostname, but this require, that the cert covers it.

]]>https://forum.netgate.com/post/1199970https://forum.netgate.com/post/1199970Wed, 18 Dec 2024 17:50:49 GMT