• 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.

ssl on subdomain failure.

J

jmi

Guest
set up IP in plesk (10.0.1 security patched)
set up domain in plesk we will call it mydomain.com
associated domain to exclusive IP
created sub-domain shop.mydomain.com
created ssl cert CSR for subdomain
obtained SSL cert and CA and added them to plesk
associated IP address cert in plesk

Now, what should have happened is that when someone comes to the subdomain it should recognize if it's https: or http: and serve up the page.

What happens is:
- someone going to http://shop.mydomain.com/ gets the pages served up from the sub-domain
- BUT -
- someone going to https://shop.mydomain.com/ gets the pages served up from https://www.mydomain.com/

So, why is https:// not serving up the sub-domain structure for which the SSL has been licensed?
 
Back
Top