Hey every one I have a problem that I have been banging my head against for the past few days and its driving me crazy!
First off I have been using the as taro UTM for years now and absolutely love it. But I figured it was time to clean house and do a fresh install (home license) and clean up all the left overs from previous products. it took me all of an hour to get up and running again... Except for my website. It was fairly simple and straight forward before setting up a real server and then creating a virtual server and tada!!! it was externally accessible. Not so much this time.
I have replaced the site with a very simple site consisting of a single black pixel to aid with testing externally.
I setup the real webserver as follows
host= LAN IP address of my web server
type= http
port= 80
advanced=Enable HTTP keepalive
the virtual web server as follows.
interface = internal
type= http
port= 80
domain = blog.domain.com
FW profile = None
Advanced = nothing
In the WAF logs the only thing i see is the following
2014:05:25-07:19:12 rmt-asg01 reverseproxy: srcip="127.0.0.1" localip="127.0.0.1" size="51" user="-" host="127.0.0.1" method="GET" statuscode="200" reason="-" extra="-" exceptions="-" time="283" url="/lb-status" server="localhost" referer="-" cookie="-" set-cookie="-"
2014:05:25-07:19:34 rmt-asg01 reverseproxy: srcip="127.0.0.1" localip="127.0.0.1" size="51" user="-" host="127.0.0.1" method="GET" statuscode="200" reason="-" extra="-" exceptions="-" time="287" url="/lb-status" server="localhost" referer="-" cookie="-" set-cookie="-"
I am able to ping the external DNS blog.domain.com and it looks up the correct external IP and responds to ping. But I get time out errors when I try to navigate to the site with a web browser. The site is accessible from all internal computers.
What am I doing wrong?
This thread was automatically locked due to age.