Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In haproxy settings there is frontend which bind on 443.

The problem is inside this frontend I need to use acl rules in order to distinguish traffic based on server_name.

However, if I am understand correctly I can't use acl together with 443.

If there any way to send ssl traffic to different backends regarding their hostname?


share|improve this question
up vote 1 down vote accepted

For using haproxy with ssl (443) you need to use stunnel because haproxy does not support ssl it self.

share|improve this answer

In the development branch, we have support for SNI (server name indication) which allows a TCP-mode haproxy to know what server an SSL client is targetting if the client uses the extension too (which all recent clients do). Otherwise as indicated by B14D3, you have to decipher the traffic as it's the purpose of SSL to prevent anyone from seeing what's exchanged in it.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.