I am trying to publish an internal web server over the WAF. The setup is as follows:
I can access the website and login, so that worked. The first problem was that any link on the website pointed to the internal hostname. I resolved this by activating "Pass host header" in the virtual webserver. Now the links point to the correct hostname but the custom port (8089) is missing so when I click on a link it tries to establish the connection via port 443. What am I missing?
UTM/SG don't support rewriting URL this way ... as i know.
i would try to use Port 443 for Virtual webserver (if not used already).
Sophos Solution Partner since 2003 If a post solves your question click the 'Verify Answer' link.
I already use Port 443 for Exchange services and only have one public IP address, so I'm guessing the only other option here is DNAT?
It shouldn't be a problem having more than one server listening on the external 443 port. The mapping is done by WAF based on the certificate and the real server.I host several external domains all resolving to one IP / port 443Internally they are mapped to ports 8281, 8282 etc.