- Article Type: General
- Product: Voyager
Configuring Apache and WebVoyage for sites with different internal and external IP addresses
For example, imagine that your server's internal IP is 10.0.0.1 and its external IP, for outside users, is 220.127.116.11. You also use the hostname, voyager.college.edu, to connect to WebVoyage:
1) In the /m1/shared/apache2/conf/ConfiguredVirtualHosts/xxxdb_vwebv_httpd.conf file, the server hostname should be used for ServerName in order to map to the internal IP address, instead of using the external IP address. If the external IP address is used, it can't map to the internal IP address.
ServerName voyager.college.edu (Correct)
ServerName 18.104.22.168 (Wrong)
2) For the Virutal Host portion of the httpd.conf file, use the internal IP address, shown as below:
3) All other connections to the server must use "localhost", 127.0.0.1, or the internal IP address of the server. Examples:
The host of the voyager XServices.
# configuration for a Voyager OPAC connection
The essential point is that every setting on the server itself should refer to the internal address that the server is actually using. The external address is bound to a network device, like a router, that forwards traffic into the internal network, where the internal address is used. The server itself is never aware of the external address.
- Article last edited: 3/19/2015