• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Question set up a subdomain for an alias domain - SSL certificate

W4ru

Basic Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.64 Update 1
Starting point:
I have a domain.tld and the alias domain.tld2
A wordpress with language switcher is running on it and everything is working as it should.

Now I was planning to use this variant for a special project
sub.domain.tld and sub.domain.tld2

The problem is that despite the wildcard certificate *.domain.tld and the corresponding certificate for domain.tld2, I cannot get an SSL connection to sub.domain.tld2, because apparently *.domain.tld2 is not certified!

Is this an error by design? How can I also integrate the subdomains into the certificate for the alias domain(s) via *?

Setting up the domains separately in Plesk would be the worst solution.

I am glad for any advice!
 
Back
Top