NethServer Version: 7.4
Module: Let’s Encrypt
I’m pretty familiar with the use of Let’s Encrypt in SME, but the development there is on dehydrated (which I’d recommend you consider, along with acme.sh, rather than certbot–either of those is much more lightweight, and the extra features of certbot don’t seem to be at all necessary in this application). Seeing Let’s Encrypt integrated into the server manager is certainly nice, but it leaves a few questions:
- It looks like the process to get a cert is to go to Server Certificates -> Request Let’s Encrypt certificate, enter the desired hostnames, and click the red button. Once obtained, set it as the default cert. Is that all there is to it?
- It would then follow that, in order to add new hostnames/domains, you’d just repeat this process, adding whatever FQDNs you wanted to add?
- Is the cert always going to be saved in the same location? It appears that the Let’s Encrypt cert, after being issued, is copied to
/etc/pki/tls/certs/localhost.crt. Is it always going to be at that path?
- Does issuing a Let’s Encrypt cert also schedule a task to renew it?