Bill,
Can't send you a sample of my working config files but I'll try and give you a little help. Have you tried to put multiple Listen directives into your single conf file? I still have seperate conf files using httpd.conf and ssl.conf. I have a Listen directive in each.
Something like this should work
Listen 192.168.1.2:80 Listen 192.168.1.2:443
If you only had one Listen directive along with your NameVirtualHost directive I suspect that would cause an error since the port in the Listen directive and NameVirtualHost directive did not match.
If that was not the problem however I'm not sure what else it could be.
Ryan
On 6-Jun-06, at 11:08 AM, Bill Angus wrote: Ryan this is great news! When working with this, I got rid of the include files by putting together a single config file which included all the desired portions. I tried placing the "listen 443" directive everywhere I could think of that made sense. No matter where it showed up I got an error and apache would not load. I found that I could have either NameVirtualHost *:80
or listen 192.168.1.2:443 ... but not both directives in the same file. With both directives, the service always crashed at startup. My platform is Win2k pro -- but it should make no difference from win2003. Can you post a sample of your working config?
Thanks! ----- Original Message ----- Sent: Tuesday, June 06, 2006 7:17 AM Subject: Re: [users@httpd] VirtualHost
1st, regarding an earlier comment in this thread... it matters what your platform is: In a windows environment (as far as I could tell after 2-days worth of messing around with configs... ), you cannot actually have name-based v-hosting on port 80, as well as a single SSL v-host on 443, unless you set up two separate windows services, one for SSL on port 443 and one for port 80.
I can say that this is not true. On a Windows 2003 server and Apache 2.0 we have several name based vhosts on port 80 and one vhost on port 443 for ssl. 2nd... from what you have written, is it possible that you might not have configured your domain DNS properly? If so, this might have affected whether your CSR was correct when you got your SSL certificate. You want to set up your domain DNS as something like www.yourdomain.com (which you will serve on port 80). You will want to set up a sub-domain DNS record for secure service (something like secure.yourdomain.com ). You will want to generate a CSR and get a certificate for secure.yourdomain.com (not www.yourdomain.com)
If you are able to configure the vhosts properly on both 80 and 443 this is not required. The vhost on each port can have the same domain name and the http vs https will direct the request to the proper vhost.
Follow the advice of Owen and Matthew and look for an Include directive in your httpd.conf file to see where the other vhost it being declared. I suspect it is the file ssl.conf.
Ryan
|
