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

Resolved Domain with 100 domains alias: Let's encrypt problem

Erwan

Regular Pleskian
Plesk Onyx / Centos
===========
Hello,
We have a problem with a website on which we have 100 domains alias (since a lot of year).
We want now use "https" with Let's Encrypt.
So we select domain alias to secure (all) and we validate.
After a lot of minutes, we have an error:

"operation too long"

If we gradually add alias domains, we have the same problem from the 20 or 25th domain...

How can we solve this?
Is there a command line to made the opration?
 
I doubt that so many domains will work at all, and there is nothing that Plesk can do about it.

The "certificate alternative name" property of an SSL certificate is limited to 4096 bytes, thus there is an ultimate limit on how many domains you can place within a single cert.
That is also why most official signers (Digicert, Comodo and co.) do no offer SAN certificates for more that 50 domain names.

So yeah, while 100 domains may work if they are very short, that many will easily break the 4kB limit in most cases.
 
Back
Top