- Plesk Onyx for Windows
Why it is not possible to establish SSL connection to IP address if a default website is assigned on Plesk for Windows? While with Plesk for Linux it is working fine.
IP:Port SSL binding has higher priority than
Hostname:Port SSL binding.
For example, configure two websites with SSL:
sni.example.comwith SNI (Hostname:Port) SSL binding
cert_sniwhich resolves to
non-sni.example.comwith legacy (IP:Port) SSL binding 203.0.113.1:443:* and certificate
On accessing to
https://sni.example.com - the certificate
cert_non_sni will be provided by the IIS instead of
That is why Plesk does not create legacy (IP:Port) SSL binding on websites.
For details see Microsoft blog article at https://blogs.msdn.microsoft.com/kaushal/2012/09/04/server-name-indication-sni-with-iis-8-windows-server-2012/