Server Certificate Manager

Hello to all,

Because I’m also a “Zentyal refugee” I must refer to another facility that not exist on NS: Server Certificate Manager.
Zentyal generate certificates for the main domain and also for every virtual domain that you create on the server (email domains in my case).

The certificate issued by NS is only for the main/initial Server name (hostname and domain) and works perfect.

But in case (my case) that you have other domains (email domains), the certificate is not valid (please see the images below).

Can Let’s Encrypt make this possible ?

"When Let’s Encrypt is enabled, the system will create and automatically renew:

- one certificate for server FQDN
- all enabled server alias will be added as SAN ( to the FQDN certificate
- one certificate for each domain enabled inside the certificates database"

What it means ***“inside the certificates database”***?

If NO, there is a workaround for this? HOW?


1 Like

You should refer to this wiki page:

See “Certificate for server alias (optional)” section :wink:

Hi Giacomo,

Thank you for your answer.

I read what you wrote there but there are two different things (or not?):

  • server alias(es)
  • each domain enabled inside the certificates database

I thought that is not about server alias(es) because the virtual domains are not aliases for main domain (are not in NS -> DNS -> Server alias), there are individual/different domains. Or is it really about it and I misunderstand?

In this case, all email domains created in NS -> Email -> Domains will be “seen” by Let’s Encrypt as “server aliases” as is write here: “The FQDN certificate can be extended to be valid also for extra domains configured as server alias. This feature is called SubjectAltName (SAN)” and all those domains are “enabled inside the certificates database”?


I must to add all email domains also in NS -> DNS -> Server alias as is write here: “Create a server alias inside the DNS page, then enable Let’s Encrypt on the newly created record.” ?

But this will be OK? Will be not generate errors?

Sorry for those questions but I try to learn and understand.


Basically you have two options:

  1. one certificate valid for one or more hostnames

  2. one certificate for each domain

  3. uses SAN, I choose it when I have different names for a server, like and

  4. uses SNI. you will have many certificates, one for every host, that you should assign to relevant services

AFAIK, support for 2. has been removed from the package.
I think you need 2., we need to understand how to put back the code.
Am I right?

Hi Filippo,

Yes, you are right, I think I need 2.

The server is “”. On this server, are hosted different email domains which are not aliases for “”.
All domains are registered on our external DNS server ( as FQDNs.

I think this will be usefull also for web hosting (let’s say “” with many www domains).