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

Issue Subject Alternative Name for mail subdomain missing

nilsglow

New Pleskian
Hi!
We try to secure our mail server (IMAP) with Letsencrypt. Plesk says that 'Mail access" (IMAP, POP, SMTP) is secured. But the certificate does not contain the mail.example.tld subdomain as a Subject Alternative Name. We told our customers to access the mail server via this subdomain...

Thanks,
Nils
 
It seems like that problem only occurs when NOT using wildcard certificates... But shouldn't it work with a SAN certificate including mail.example.tld as well?
 
Back
Top