• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

SNI bug re-added in latest MU?

LinqLOL

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
 
We do not touch anything in the latest microupdates related to SNI. This issues has been fixed in MU#17.
If you faced this issue with installed MU#21 - please send me in PM login credentials on your server and step-by-step instruction for reproducing this issue.
 
You must log in or register to reply here.

Similar threads

C
Question Strange SNI (?) issue related to IPv6 (?)
Replies
2
Views
2K
Carbon Dioxide
C
B
Issue Default Page Certificate issue (no new cert)
Replies
1
Views
2K
Peter Debik
P
skibidi
Forwarded to devs DNS template placeholder aren't replaced with right IP address when using specific muli IP setup
Replies
11
Views
3K
Peter Debik
P
S
Apache does not apply .htaccess directives for certain files after migration through Plesk Migrator
Replies
2
Views
3K
NewGate
N
DerDanilo
Issue Let's Encrypt and "Assign the certificate to mail domain" problems and AutoDiscovery issues caused by this
Replies
7
Views
4K
Kaspar
K
Back
Top