LinqLOL
Basic Pleskian
Hi (Igor especially),
Is it possible that a SSL SNI bug had re-added in the lastest MU updates? The problem in a nutshell. A website with an SSL website on a dedicated IP address was threated as an SNI (shared SSL website) and is served with the default ssl certificate.
With new sites added I see the same behaviour again as it was when I submitted the bug (ticket #1732555)
Steps to reproduce:
* Create website
* Assign dedicated IP address to it
* Add an SSL certificate under the specific website
* Test website at https://ssltools.websecurity.symantec.com/checker. The SAN shows the default certificate for websites instead
Is it possible that a SSL SNI bug had re-added in the lastest MU updates? The problem in a nutshell. A website with an SSL website on a dedicated IP address was threated as an SNI (shared SSL website) and is served with the default ssl certificate.
With new sites added I see the same behaviour again as it was when I submitted the bug (ticket #1732555)
Steps to reproduce:
* Create website
* Assign dedicated IP address to it
* Add an SSL certificate under the specific website
* Test website at https://ssltools.websecurity.symantec.com/checker. The SAN shows the default certificate for websites instead