• 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 WIldcard LetsEncrypt not covering mail.domain.com

apaunovski

Basic Pleskian
So, I have issued wildcard SSL certificates for my domains - domain1.com and domain2.com.

Both don't seem to cover mail.domain1-2.com.

Why?

Please, explain.
 
So, I have issued wildcard SSL certificates for my domains - domain1.com and domain2.com.

Both don't seem to cover mail.domain1-2.com.

Why?

Please, explain.


I use external wildcard certificates to cover that part of plesk. In my opinion it is the best solution for now
 
Back
Top