This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos UTM different HTTPS websites on one public IP


I have seen the current question has been posted in various forums but other than saying "yes this can be done" there does not appear to be any clear documentation on HOW to do this.

Can someone please help me with a document or screenshots on HOW to configure multiple SSL websites through a Sophos UTM with one public IP Address? 

Thank you in advance for your help.

This thread was automatically locked due to age.
  • In the webserver protection you can select different URLs in the virtual servers and redirect them to different real servers.

    In (public?) DNS you have to point all URLs to the same IP

  • In your Webserver configuration - each domain/subdomain will have it's own Virtual Webserver. Your interface will be the same for each Virtual server since the interface = the public IP. From there, you can configure backends ("Real webservers for path") which may or may not be the same webserver depending on your specific setup. 

  • I have created 2 separate Real Web servers and 2 separate Virtual web servers.

    I have also registered the 2 different URL's in the public DNS to point to the same Public IP Address.

    They both work, as the first one is coming through Port 443 and the second one through Port 80.

    If I change the second web server Port 80 to Port 443, it resolves to the webpage of the first web server (my Exchange OWA page)

    How do I stop this from happening?

    I have tried creating an "Additional Addresses" on the interface with its own IP Address and using this. It makes no difference, it still resolves to the first web page (Exchange OWA)

  • Thank you, Aaron. Please see my reply above.

  • Do your virtual webservers have different domains / subdomains? The virtual webserver should be selected based on the FQDN of the request.

    Have you checked the logs? 

    what version of Exchange are you trying to provide WAF for? A while ago there used to be a config guide for WAF/Exchange. I keep an old config guide around in case they disappear from the web. Let me see if I can find a link.

    EDIT: Shame. It looks like the config guide has been put behind a paywall "SophServ." let me know what version of Exchange you're running and I can see if I can get a copy to you. Someone also has a tutorial online as well:

  • They are both part of the same Domain, "" and "" 

    I have a "" certificate and I also have a "*.mydomain .com" wild card certificate.

    I am using the mail certificate for Exchange and the wild card for the second web server.

    The Exchange server has been working for 3 years through the UTM, with no issues at all, so the configuration is good.

    It was Exchange 2013 I have upgraded to Exchange 2016 about 6 months ago, but as I say, Exchange works fine.

    It is trying to add a second web server that has been a challenge for me?

    Thanks for the link.

  • so the problem is when you go to it is redirecting you to something else? Which virtual webserver is the request being handled by (should say in the logs). Do both virtual webservers have the same backend or different "real" servers?

  • "so the problem is when you go to it is redirecting you to something else?" - Yes it goes to the OWA page.

     "Do both virtual webservers have the same backend or different "real" servers?" - Different "real" webservers.

  • As a trouble shooting step, you could try disabling your owa front end (virtual server) and seeing what happens (error vs going to the correct backend/real server. If it works when the owa virtual webserver is disabled, you might have a site path routing issue. 

    A less destructive/intrusive way to gather info would be to watch the logs while the request comes in and see what it says, what virtual server is handling the request and what backend it's selecting. 

  • Thanks Aaron.

    I have been rubbish at reading the Sophos logs. Which log should I be looking at whilst connecting to the web page?