I don’t know if someone has found a way to make Certbot run a command-line version of the import process automatically. That’s not the experience we would prefer for Certbot users to have, because one goal of Let’s Encrypt is to try to make certificates renew automatically without human intervention each time. The aliases (symbolic links) are part of that design because their targets get updated automatically to point to the renewed certificates, so that a server application can point to the link instead of to a particular version of the certificate, and can receive the new version of the certificate automatically upon renewal.īut, if you have to use “Import a Certificate Identity”, it’s not very plausible that Certbot’s renewal will also perform this step automatically it will probably have to be repeated manually. The process that you had to follow suggests that Certbot’s integration with macOS is not that great because the design of Certbot is to update these files automatically when your certificate is near expiry (if you regularly run certbot renew from cron or another scheduling tool). I’m glad you were able to get your certificate imported. I am uncertain if this is what is causing the mentioned folder to not be created, but I don’t want to continue following the guide until I resolve this issue. As Homebrew does not drop privileges on installation you would be giving all build scripts full access to your system. Using Homebrew to install dependencies.Įrror: Running Homebrew as root is extremely dangerous and no longer supported. Requesting to rerun /Users/administrator/letsencrypt/letsencrypt-auto with root privileges.īootstrapping dependencies for macOS. I get the following output: server:~ administrator$ ~/letsencrypt/letsencrypt-auto -help -debug When I run: ~/letsencrypt/letsencrypt-auto -help -debug

After installing brew and attempting to install the LE client, I’m finding that the /etc/letsencrypt folder is not being created. I’m following the same guide as I did before and encountering an issue on the first step. I had to perform a fresh install of the OS and Server. Fortunately, with the help of the community, I was able to get the LE cert downloaded and working! I had a previous post on problems I had with getting an LE cert downloaded and working with the company Wiki on a Mac Pro running MacOS server.

Mac os 10.12 wiki