[SOLVED] Zimbra 8.7 and letsencrypt ssl

[qadir52786]

Hi jorgedlcruz and DualBoot !

Thanks guys, I will check and confirm

Please update how did you solve the problem

as cant open wiki and facing some problem while upgrading to 8.7.10

[DennisAyala]

Wiki updated

• https://wiki.zimbra.com/wiki/Installing ... ertificate

Best regards

Jorge:

I need to deploy Lets Encrypt Multi-SAN on a Zimpla multi-server environment. Is there any pre-requirements or additional steps I need in order to deploy them to all my servers?

Regards,

Dennis

[lucianoserverdo]

I had the same problem, just add the Fqdn hostname in the lets encrypt list to solve

Just as a little Note and warning: if you use the steps described in the Wiki and your Hostname Fqdn does not match the public domain name (which is pretty much always the case) after deployment of the lets encrypt certificates the ldap Server will fail to connect, since it somehow expects the local ldap Server to be able to be resolved on the public domain name and even after fixing this by adding an entry to the Hosts file it failed to connect to the local ldap Server, hence zimbra did not start anymore. Fortunately i had a Snapshot i could revert to.

Gesendet von meinem SM-N910F mit Tapatalk

[joho]

Considering how common Let's Encrypt certificates are these days (and have been, for quite some time), and what a great value they provide to system administrators and Zimbra administrators, I'm surprised there's not a function in Zimbra 8.7.x+ certificate management to simple request Let's Encrypt certificates automatically, for single domain and multii-domain (SAN) deployments, with handling of renewals, etc. Surely, it would be the best place for such things, rather than third-party scripts that may or may not work depending on which patch level of Zimbra you happen to have installed.


-joho

[Abhishek]

The case solved! Deployed and confirmed!! Thanks all!

Hi Amatu,
I am facing same issue, please give me some direction how did you fixed "zmcertmgr: ERROR: no longer runs as root!" error.

Thanks,
Abhishek