Web Server - Troubleshooting - NaviCOPA

Top  Previous 

I cannot access NaviCOPA from inside my network using for example http://192.168.22.55

 

1.Check that you actually have connectivity to the server machine - try pinging it from a Command Prompt
2.Do you have the default path disabled?
3.Do you have NaviCOPA configured only to accept secure (HTTPS) connections?
4.Are you using a non-standard port number? If using say, Port 81, you must access the server using a URL like http://192.168.22.55:81

 

I cannot access NaviCOPA from outside my network (ie via the internet) using an IP Address, eg http://194.158.2.36

 

1.Do you have the default path disabled?
2.Do you have NaviCOPA configured only to accept secure (HTTPS) connections?
3.Do you have a router? If so, is it set to forward connections from the internet to your server machine?
4.Are you using a non-standard port number? If using say, Port 81, you must access the server using a URL like http://194.158.2.36:81

 

I cannot access NaviCOPA from the internet using a machine name, eg http://www.myserver.com

 

1.Is there a DNS entry for this name - check that you can ping it by name.
2.Have you configured a Virtual Host with this name on the Hosts tab?
3.Do you have the default path disabled?
4.Do you have NaviCOPA configured only to accept secure (HTTPS) connections?
5.Do you have a router? If so, is it set to forward connections from the internet to your server machine?
6.Are you using a non-standard port number? If using say, Port 81, you must access the server using a URL like http://www.myserver.com:81

 

I cannot access my virtual host www.myhost.com from inside my local network

 

This happens with some routers. Here is a workaround:

 

The HOSTS file is used by the Operating System to find IP Addresses corresponding to machine names. If not found there, the OS will go to the configured DNS machines. You can add any names you wish to it, together with the IP Address you wish to be used for each name.

 

The HOSTS file (note it has no file extension) is located:

 

Windows 95/98/ME: C:\Windows

 

Windows XP/Vista: C:\Windows\System32\Drivers\etc

 

If HOSTS does not exist, there should be a sample file called HOSTS.SAM: rename this to HOSTS.

 

Open HOSTS with Notepad (or any other text editor): it should have a brief explanation and one entry for the localhost (the loopback to the machine itself). Add an entry like this:

 

www.mydomain.com        192.168.1.1

 

Note that the gap between the name and the IP Address should be at least one space or tab.

 

Save the file.

 

NOTE that this will only affect this machine, modify others on your network if you want them to behave similarly.

 

If you wish to check that your virtual host is accessible from the internet, set your browser to use an external proxy (typically that of your ISP). Traffic from your machine will go out to the proxy, back into your network, to your server, then back by a similar route.