On Tue, November 22, 2016 22:40, James B. Byrne wrote:
>
> On Sun, November 20, 2016 12:43, Walter H. wrote:
>
>>
>> https://box.domain1.com works
>> but
>> https://box.domain2.com results in 'Certificate name mismatch'
>>
>>
>
> What are the contents of the certificate(s) you have configured for
On Sun, November 20, 2016 12:43, Walter H. wrote:
>
> https://box.domain1.com works
> but
> https://box.domain2.com results in 'Certificate name mismatch'
>
>
What are the contents of the certificate(s) you have configured for
tls? What AltSubject names, if any, do the certificate(s) support?
It is solved, I don't know why but
SNI works only with hosts that are
declared with ServerName
and not with ServerAlias
so I did the following ...
I made an include file that contained everything of the virtualhost
except the ServerAdmin and ServerName declarations
and did this:
ServerAdmin
On 20.11.2016 18:33, David Nelson wrote:
It doesn't appear you have a ServerName or ServerAlias for the naked domains
(sans subdomain), so they're both being answered by the first VirtualHost entry?
this is not the problem
meant
https://box.domain1.com works
but
https://box.domain2.com
It doesn't appear you have a ServerName or ServerAlias for the naked domains
(sans subdomain), so they're both being answered by the first VirtualHost
entry?
> On Nov 20, 2016, at 9:24 AM, Walter H. wrote:
>
> Hello,
>
> is Apache 2.2 which is part of the CentOS
Hello,
is Apache 2.2 which is part of the CentOS distribution capable of SNI?
I have troubles that are coming from server side (CentOS 6.8, Apache 2.2.15)
just did 'yum update'
in
/etc/httpd/conf/httpd.conf
I've the following
NameVirtualHost ipaddr:443
Include
6 matches
Mail list logo