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

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