• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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