<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Is it possible to have two different shared front-ends with different types?]]></title><description><![CDATA[<p dir="auto">Way back in time, I set up HAProxy to use TCP passthrough via a "shared" front end to multiple back-end domain servers. I call it shared but the "shared" front end setting is not set.</p>
<p dir="auto">That pseudo shared front end is of type ssl/https (TCP mode).</p>
<p dir="auto">Yes, I know that doesn't use HAProxy "correctly" since it doesn't offload TLS processing to the proxy.</p>
<p dir="auto">Now, I have a new domain for which I would like to offload TLS processing. No problem, you might think: just add a new front end of type http/https (offloading) for that domain.</p>
<p dir="auto">The rub is that I want that new domain to also be proxied on inbound TCP 443 which the existing "shared" front end already listens on.</p>
<p dir="auto">My question is, is there any way to add a second front end of a different type that listens on an existing HAProxy front end port?</p>
<p dir="auto">I think the answer is no -- but in case there's something I haven't thought of...</p>
<p dir="auto">FWIW, I cannot switch the current front end to offloading due to backend server requirements.</p>
<p dir="auto">Maybe this screenshot will explain better what I would like to acheive.</p>
<p dir="auto"><img src="/assets/uploads/files/1768134690310-2026-01-11_07-18-02-resized.png" alt="2026-01-11_07-18-02.png" class=" img-fluid img-markdown" /></p>
]]></description><link>https://forum.netgate.com/topic/199790/is-it-possible-to-have-two-different-shared-front-ends-with-different-types</link><generator>RSS for Node</generator><lastBuildDate>Tue, 16 Jun 2026 09:41:18 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/199790.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 11 Jan 2026 12:33:13 GMT</pubDate><ttl>60</ttl></channel></rss>