• 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 Lets encrypt for mails: separate certificates for multiple domains to avoid invalid certificates

danieldaniel

New Pleskian
Hi,

I use Onyx 17.8.11 and have several Domains Routing to plesk.

Problem: When a customer adds their email account to Outlook, iphone,.. using "mail.customer-domain.com" they receive an error: "Invalid Certificate: This certificate belongs to a different site"

Reason is that the certificate is from my "main Domain" and not "customer Domain". The message is clear to me.

However, how do I achieve to avoid such a message? My idea was to create separate certificates, but even then I stop because I have no idea how to handle it as I don't see Options for this? I also read on a post from 2016 that it's not possible, but maybe it has changed.

So how can we avoid/fix it?

Regards
 
Back
Top