<?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[Reverse Proxy for Multiple Domain Names and Multiple Servers Behind pfSense]]></title><description><![CDATA[[[topic:post-is-deleted]]]]></description><link>https://forum.netgate.com/topic/142597/reverse-proxy-for-multiple-domain-names-and-multiple-servers-behind-pfsense</link><generator>RSS for Node</generator><lastBuildDate>Sat, 17 Oct 2026 09:22:46 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/142597.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 16 Apr 2019 03:04:36 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Reverse Proxy for Multiple Domain Names and Multiple Servers Behind pfSense on Tue, 16 Apr 2019 04:53:00 GMT]]></title><description><![CDATA[<p dir="auto">HAproxy is certainly the path there but you're going to want to get rid of all of those port forwards. HAproxy frontend listens on WAN address, looks at the connection details, and proxies to the appropriate backend servers. You don't have to port forward, you just open 80/443 so HAproxy can receive connections.</p>
]]></description><link>https://forum.netgate.com/post/837452</link><guid isPermaLink="true">https://forum.netgate.com/post/837452</guid><dc:creator><![CDATA[Derelict]]></dc:creator><pubDate>Tue, 16 Apr 2019 04:53:00 GMT</pubDate></item></channel></rss>