View Complete Thread | FoxWeb Forum Home
Date:    Msg ID:   
From:    Thread:   
We are using version 2.11.  We are only seeing errors in the Foxweb error log.  The IP addresses in the virtual servers grid are internal IP addresses (, and the IP address we see in the error message is an external IP address that matches the IP assigned to the Server Name value for our default program root.  Our firewall handles this translation and this has worked fine since we started doing this over a year ago.  Again, no clients have complained about not getting to a web page but I would just like to know if there is a way to track down where these requests are originating from, such as the full URL that they were trying to access (if that is available).  Thanks.
Sent by FoxWeb Support on 01/31/2007 09:25:43 PM:
Please always specify the version of FoxWeb you are using.
This error indicates that the host name, or IP address in the URL does not match any of the ones specified in the Virtual Servers grid in the FoxWeb Control Center.  Are you seeing the error in your own browser, or in the FoxWeb error log?
FoxWeb Support Team email
Sent by on 01/31/2007 01:41:30 PM:
About a month ago, we started receiving the error message "No program root has been configured for domain..." multiple times throughout the day.  We have the Foxweb control center setup with internal IP addresses (ie. and have our firewall translate external IP addresses to internal addresses.  The address shown on the error message is an outside IP to our default website. 
We have not made any changes to our Foxweb configuration in over a year.  We have not heard from any users having trouble accessing any sites that run under the default program root.  Also, all our Foxweb apps write to a log file when pages are requested, and I cannot find a pattern with certain sites being in use when this happens (there are times when no other Foxweb sites are accessed within 10 minutes before or after of this error message). 
Please let me know if there is anything we can do to troubleshoot this problem.