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

Question Let's Encrypt for aliases for admin panel

VirtualCed

New Pleskian
Hi there,

I moved customers from a server to another one.

The users from server A used to login using control.mydomain.com and the users from server B used to login using panel.mydomain.com

Now, they are all going to user panel.mydomain.com (at least they should). But users are what they are and a lot of them are still using control.mydomain.com. The domain is linked to the same IP.

But the SSL certificate is only for panel.mydomain.com. That causes a warning for the panel and also for the mails as there is a mismatch between name and certificate.

Before telling to all the users to change their favorite AND to change their server settings, I'd like to know if there is a possibility to have both subdomains secured for panel AND for mail server.

Best regards
Cedric
 
Back
Top