• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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