• 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 Plesk Migration results in wrong SSL certificate for all mail subdomains

Maya K. Herrmann

New Pleskian
Hello dear people,

we did a migration from one virtual server with Plesk 12 to another. The new one runs Plesk Onyx v17.8 on an Ubuntu 16.04 LTS machine. I would say that the migration process itself ran pretty well, but afterwards we discovered, that suddenly all mail subdomains from our clients are using a wrong SSL certificate (one from Let's Encrypt, that already was installed on the old virtual Server. This certificate was installed and is used by the domain, which is also listed as the very last entry in the domain listing in Plesk Admin Area).
We searched all Plesk Backend, to resolve that problem, but somehow, we don't manage and lost track of where to look. Even trying to delete the certificate is not working, because of Plesk's error message, that this certificate is used on various domains (yeah, too bad that is!!!).
Does anybody know how to resolve this issue? It is fairly urgent since our clients start to freak out…
Thank you very much for any hint

Maya
 
Question: is it possible, that every mail.tld.com serves a standard ssl certificate (let's encrypt or even self-signed), which is signed for the exact correct mail.tld.com subdomain? We are heaving real issues here… maybe it is possible to change settings on Plesk console level? But I very much would need help there
Thanks!
 
Back
Top