.conf
> (or ssl.conf, or vhosts.conf whatever you prefer), one per each IP
> (). Do not enable NameVirtualHosts for them. Place
> SSLCertificateFile and SSLCertificateKeyFile directives inside your
> VirtualHosts. Remove "default" section.
> Then it should work.
>
> On 9/
(). Do not enable NameVirtualHosts for them. Place
> SSLCertificateFile and SSLCertificateKeyFile directives inside your
> VirtualHosts. Remove "default" section.
> Then it should work.
>
> On 9/12/06, milktoast <[EMAIL PROTECTED]> wrote:
>>
>> Right,
>>
>>
Right,
Can I get a second IP address on the router and pass that traffic to a
second IP on the server and get it to work?
Serge Dubrouski wrote:
>
> On 9/12/06, milktoast <[EMAIL PROTECTED]> wrote:
>>
>> I am aware of this... thus my question how should it look to
I am aware of this... thus my question how should it look to get two
certs on one server?
If it looks like this then it will work perfect for www.foo.com but
won't work for bar com. User will receive an error saying that bar.com
uses certificate for foo.com.
The rool is easy: one cert per
Serge Dubrouski wrote:
>
> If both server share one IP using NameVirtualHost feature then there
> is no way to have different certificates for them.
>
> On 9/12/06, milktoast <[EMAIL PROTECTED]> wrote:
>
>
--
View this message in context:
http://www.nabble
I have read up on using multiple SSL certs on one server but the thing that
no one addresses is how this works on a server behind a router that uses
NAT.
Example
Server 1 has two domains www.foo.com and www.bar.com
Both are functional using IP based virtual hosts using 192.168.1.50
The server
