Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    HA Proxy, same server multiple ports (Turnkey Linux)

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    4 Posts 2 Posters 216 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • CreationGuyC
      CreationGuy
      last edited by

      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

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @CreationGuy
        last edited by

        @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.

        CreationGuyC 1 Reply Last reply Reply Quote 0
        • CreationGuyC
          CreationGuy @viragomann
          last edited by

          @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.

          V 1 Reply Last reply Reply Quote 0
          • V
            viragomann @CreationGuy
            last edited by

            @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.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.