I would think you need one NameVirtualHost 1.2.3.4 and then in your SSL 
section just use the same IP <VirtualHost 1.2.3.4:443>
dns:
www  IN A 1.2.3.4
www1 IN A 1.2.3.4 

secure IN A 1.2.3.4
Lanny 


Robert Mazur writes: 

> Thanks for the response Eric. 
> 
> I might have confused the issue.  My goal is to have one ip address
> listening for two http: sites and one https: site.  I think I read that you
> can host multiple sites using VH, but only one can be https:  Did I possibly
> misunderstand that? 
> 
> Basically....I have always hosted 3 sites with one ip address using VH.  Now
> one of them needs SSL for credit cards.  I am pretty sure I can change one
> to use SSL, and still have all three on the same ip address, no?  It is
> likely I have misled myself....please let me know if so! 
> 
> Thanks,
> Rob Mazur 
> 
> ----- Original Message -----
> From: "Eric Paynter" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>; "Robert Mazur"
> <[EMAIL PROTECTED]>
> Sent: Tuesday, October 02, 2001 8:21 PM
> Subject: Re: ServerName Problem (I think) 
> 
> 
>> I don't have the full answer to your problem, but a glance at your configs
>> shows one problem: you can't have more than one virtual host name per IP
>> using SSL. If you want to host 3 domains on SSL, you need 3 IPs assigned
> to
>> your webserver. 
>>
>> -Eric 
>>
>> On October  2, 2001 06:42 pm, Robert Mazur wrote:
>> > I have FAQ'd and mail archived myself to death....still have this
> problem
>> > though...
>> >
>> > TRYING TO:
>> > Turn my Apache/tomcat install (virtual hosting 3 sites) into a SLL-aware
>> > Apache server.
>> >
>> > RESULT:
>> > ssl_engine_log says:
>> > <snip - all good data saying ssl is coming up, then...>
>> > (servername.somedomain.com:443) RSA server certificate CommonName (CN)
>> > `www.mydomain.com' does NOT match server name!?
>> > This is true, but the server name does not have to be the domain name of
>> > the site, does it?
>> >
>> > DETAIL:
>> > After a LONG battle getting "apachectl startssl" to launch (including it
>> > asking me for the password) without errors,
>> > I can not get a secured page to come up. Instead I get a Page Not Found,
>> > and "DNS server not found" error
>> > in the browser. No errors on the server.
>> >
>> > To make my httpd.conf, I took the resulting "httpd.conf.original" and
>> > modified it for my virtual hosting and such. Bascially, I copied the
> whole
>> > ssl block at the bottom of httpd.conf.original, and pasted into my
> original
>> > httpd.conf. I have 3 virtual hosts(two shown below). I added just two
>> > directives to my virtual host section of the doamin that  needs ssl
>> > support, like:
>> >
>> > <VirtualHost 63.229.30.179>
>> >     ServerName servername.somedomain.com
>> >     ServerAlias www.mydomain.com
>> >     DocumentRoot "/usr/local/apache_1.3.12/htdocs/mydomain"
>> >     # ----- next two were added -------------
>> >     SSLCertificateFile /<path_to_my_crt_file>
>> >     SSLCertificateKeyFile /<path_to_my_key_file>
>> >     DirectoryIndex welcome.html
>> > </VirtualHost>
>> > <VirtualHost 63.229.30.179>
>> >     ServerName servername.somedomain.com
>> >     ServerAlias www.differentdomain.com
>> >     DocumentRoot "/usr/local/apache_1.3.12/htdocs/differentdomain"
>> >     DirectoryIndex welcome.html
>> > </VirtualHost>
>> >
>> > So I guess I know I have a ServerName issue due to the ssl_engine_log
>> > telling me:
>> > (servername.somedomain.com:443)RSA server certificate CommonName (CN)
>> > `www.mydomain.com' does NOT match server name!?
>> > The servername in my Apache install has always been:
>> > ServerName servername.somedomain.com
>> >
>> > But due to this error I switched it to:
>> > ServerName www.mydomain.com
>> >
>> > However, the ssl_engine_log is getting something completely different
>> > (servername.mydomain.com). Where is it reading this ServerName from?
>> >
>> > What am I missing, or forgetting? Is there something else I need to do
> so
>> > that my www.mydomain.com knows it can be preceeded by
>> > an https.
>> >
>> > Any hints or thoughts?
>> > Thanks so much - Rob
>> > p.s. I should be able to just call a secured page like this, right?:
>> > https://www.mydomain.com/welcome.html
>> >
>> > ______________________________________________________________________
>> > Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
>> > User Support Mailing List                      [EMAIL PROTECTED]
>> > Automated List Manager                            [EMAIL PROTECTED] 
>>
>> --
>> arctic bears - email and name services
>> 25 email addresses@yourdomain CA$11.95/month
>> DNS starting at CA$3.49/month - domains from CA$25.95/year
>> for details contact [EMAIL PROTECTED] or visit
> http://www.arcticbears.com
>>
> 
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
> User Support Mailing List                      [EMAIL PROTECTED]
> Automated List Manager                            [EMAIL PROTECTED]
 


 -------------------------------
Lanny Baron
http://www.FreeBSDsystems.com
http://www.freedomtc.com
Toll Free 1.877.963.1900 
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
User Support Mailing List                      [EMAIL PROTECTED]
Automated List Manager                            [EMAIL PROTECTED]

Reply via email to