# Routing problems with multiple domains and tcp/http frontends

**URL:** <https://discourse.haproxy.org/t/routing-problems-with-multiple-domains-and-tcp-http-frontends/6163>\
**Category:** Help!\
**Created:** [January 21, 2021, 11:39am UTC](https://discourse.haproxy.org/t/routing-problems-with-multiple-domains-and-tcp-http-frontends/6163 "2021-01-21T11:39:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [January 21, 2021, 7:15pm UTC](https://discourse.haproxy.org/t/routing-problems-with-multiple-domains-and-tcp-http-frontends/6163/2 "2021-01-21T19:15:58Z")

</div>

The certificates must be distinct and must not overlap.

Also see:

> [@Random routing issue (tcp, sni, http/2)](https://discourse.haproxy.org/t/random-routing-issue-tcp-sni-http-2/6148/4):
>
> Yes, the symptom is your are connecting to something that belongs on backend X, which works and then the browser needs something from backend Y, but it will reuse the same session that still is going to backend X, because the certificate on backend X covers the hostname that according your rules would actually go to backend Y. They can’t overlap is the point, this is not necessarily related to wildcard certificates, it’s just easier to hit this issue with them. The point is there be a hostname…

---

_[View the full topic](https://discourse.haproxy.org/t/routing-problems-with-multiple-domains-and-tcp-http-frontends/6163)._