# Route https (websockets) connections with HAProxy

**URL:** <https://discourse.haproxy.org/t/route-https-websockets-connections-with-haproxy/11949>\
**Category:** Help!\
**Created:** [August 4, 2025, 3:02pm UTC](https://discourse.haproxy.org/t/route-https-websockets-connections-with-haproxy/11949 "2025-08-04T15:02:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rickard\_505](https://avatars.discourse-cdn.com/v4/letter/r/5f9b8f/32.png) [@Rickard\_505](https://discourse.haproxy.org/u/Rickard_505)\
**Post date:** [August 4, 2025, 3:02pm UTC](https://discourse.haproxy.org/t/route-https-websockets-connections-with-haproxy/11949/1 "2025-08-04T15:02:35Z")

</div>

I have a need of doing a variant of this [https://www.haproxy.com/blog/route-ssh-connections-with-haproxy](https://www.haproxy.com/blog/route-ssh-connections-with-haproxy) but with HTTPS (mix of websockets and normal https) termination and route to backends based on subdom.dom.topdom - using **ssl\_fc\_sni** (this SSH example is working for me if i provide internal IP from the client.)

I have it (the https/wesocket routing working perfectly with ACL’s and actions - but I have around 1500 backend servers so it’s starting to be a bit of a PIA to manage

i wish i could do one of the following:

_- 1 frontend and 1 backend_  
use the fqdn and resolve it internally (to get the internal IP) and connect to the server,  
advantage here is zero HA-admin after inital setup

**OR**

_- 1 frontend and 1500 backends_  
use the fqdn to name a backend and connect to it,  
advantage here is I can use HA to monitor the servers and their status, and have fallback backend

any example or links to point me in the right direction would be helpful 🙂

I use haproxy 2.9 on pfsense box - but ill be happy to swap to a dedicated HA if needed