Quote:
Originally Posted by rtwingfield
I've basically taken the configuration from the v2.0 ssl.conf file and incorporated into the ./extra/httpd-ssl.conf of v2.2.11. I've discovered a few nuances such as the <VirtualHost _default_:443> construct in v2.0 had to be changed to <VirtualHost 192.168.1.73:443> which is the IP address within the LAN, i.e., inside a NetGear FVX538 VPN Router.
|
From
http://devil/doc/apache22/mod/mpm_common.html#listen
Quote:
The Listen directive instructs Apache to listen to only specific IP addresses or ports; by default it responds to requests on all IP interfaces. Listen is now a required directive. If it is not in the config file, the server will fail to start. This is a change from previous versions of Apache.
...
|
From
http://httpd.apache.org/docs/2.2/mod...amevirtualhost
Quote:
Note
Note, that the "main server" and any _default_ servers will never be served for a request to a NameVirtualHost IP address (unless for some reason you specify NameVirtualHost but then don't define any VirtualHosts for that address).
|
And in your config snippet you have more than one VirtualHosts listen on :443 without defining a different IP.
If you look a little deeper you also see the httpd-vhosts.conf is included before httpd-ssl.conf and has two wildcard ssl vhosts.
Write for your ssl enabled vhosts a dedicated file and include them after the generic httpd-ssl.conf and make sure every SSL vhost has a dedicated IP.
Code:
<VirtualHost *:443>
DocumentRoot /www/vhosts/Archaxis.net
ServerName Archaxis.net
ServerAlias www.Archaxis.net
</VirtualHost>
<VirtualHost *:443>
# Added MAR 2010
DocumentRoot /www/vhosts/AR042SWRCAP.org
ServerName AR042SWRCAP.org
ServerAlias www.AR042SWRCAP.org
</VirtualHost>
<VirtualHost 192.168.1.73:443> # . . .the VPN router address
# General setup for the virtual host
ServerName archaxis.net:443
...