Hi,
I've been all over the web and mailling list archives, so I know multiple
SSL hosts on one machine is a problem for name-based virtual hosts, but
shouldn't IP aliasing and IP-based virtual hosts solve this?
I seem to be doing everything correctly but the certificate of the top
virtual host is
Hi,
I've been all over the web and mailling list archives, so I know multiple
SSL hosts on one machine is a problem for name-based virtual hosts, but
shouldn't IP aliasing and IP-based virtual hosts solve this?
I seem to be doing everything correctly but the certificate of the top
virtual host is
On 2/8/07, bruno alves teixeira <[EMAIL PROTECTED]> wrote:
Hi,
I've been all over the web and mailling list archives, so I know multiple
SSL hosts on one machine is a problem for name-based virtual hosts, but
shouldn't IP aliasing and IP-based virtual hosts solve this?
I seem to be doing everyt
Hi Joshua,
the certificates are now different for each virtual host - I sent a
different file earlier. I have removed the NameVirtualHost directives. I
still have the same problem. I've restarted apache after the changes and
the problem still remains, when I access 192.168.2.250 via browser, I get
On 2/8/07, bruno alves teixeira <[EMAIL PROTECTED]> wrote:
Hi Joshua,
the certificates are now different for each virtual host - I sent a
different file earlier. I have removed the NameVirtualHost directives. I
still have the same problem. I've restarted apache after the changes and
the problem
Hi there,
it's working fine after all. I guess it was the NameVirtualHost directive.
Thank you very much for help.
Take care.
> On 2/8/07, bruno alves teixeira <[EMAIL PROTECTED]> wrote:
>> Hi Joshua,
>>
>> the certificates are now different for each virtual host - I sent a
>> different file ea
