I have services (mail, web) on macOS High Sierra Server protected with a letsencrypt certificate and that works fine. I'd like to extend that use of letsencrypt to Open Directory, to fully get rid of all that self-signed stuff. But when I select my letsencrypt cert for OD, the clients won't work with it presenting me with a '2100' error.
I know they're only in public beta at the moment, but I've not seen much discussion about a easily installed QNAP app for updating letsencrypt.org certificates. I did see this thread in the QNAP feature requests forum, but barring QNAP themselves implementing it I presume with LetsEncrypt's mentality it shouldn't be too crazy a thing for someone to package a QPKG file?
- Sure But the only way you will use multiple certificates in hMailserver is to assign a different port for each certificate, otherwise the clients get the 'standard certificate', and at any rate you can only set a single 'host name' for your hMailserver.
- I have services (mail, web) on macOS High Sierra Server protected with a letsencrypt certificate and that works fine. I'd like to extend that use of letsencrypt to Open Directory, to fully get rid.
- Securing Jenkins on Mac OS X with Let’s Encrypt October 19, 2017 2018-08-10T11: DevOps and Tools When using Jenkins to build iOS applications on Mac OS X, it’s very important to ensure the server is secure – both protected from unauthorized access, and having communications secured by SSL.
Now, my certificate is for
serverhost.mydomain.tld and the server is configured as
serverhost.mydomain.tld. DNS and all that is correct.
Information on the web about 3rd party certs is generally at least 4 years old (and not helpful). So, I'm asking a fresh question here. What steps do I have to take to have OD use my letsencrypt cert in a way that it also works on clients?