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

HAproxy "Type" frontend setting

Scheduled Pinned Locked Moved Cache/Proxy
3 Posts 2 Posters 794 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.
  • V
    vinceepic
    last edited by Mar 18, 2020, 12:39 AM

    When configuring a frontend in HAProxy there are 3 types, I'm a bit confused.

    I want to forward everything that hits port 443 on the frontend to port 443 on the backend, no ssl offloading or termination, just a basic load balancer. I handle ssl on the backends.

    Do I want ssl/https(TCP mode) or just straight tcp mode? The mode I'm looking for is "SSL passthrough", but I don't see that available.

    1 Reply Last reply Reply Quote 0
    • V
      vinceepic
      last edited by Mar 18, 2020, 1:23 AM

      Just to answer my own question here, if you are reading the HAproxy docs and want what they call "ssl passthrough" for your frontend, what you want to select for the "type" is "tcp". ssl connections will be load-balanced and sent as-is to the configured backends.

      P 1 Reply Last reply Mar 21, 2020, 8:58 PM Reply Quote 0
      • P
        PiBa @vinceepic
        last edited by Mar 21, 2020, 8:58 PM

        @vinceepic
        Yes TCP mode would work.. But do you have a reason for not using "ssl/https(TCP mode)" which would give the same frontend/backend configuration regarding the passing of the ssl traffic without any changes, but would allow to set some SNI based acl's in the webgui?

        1 Reply Last reply Reply Quote 0
        3 out of 3
        • First post
          3/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received