So I made copies of the “privkey.pem” and “fullchain.pem” files in the “live” folder, and changed the file extensions to “.key” and “.crt”. pem” to MAMP PRO’s “nf” file via the “File/Edit Template” menu, but that has not helped. I added the string “AddType application/x-x509-ca-cert. They are grayed out when I navigate to them. However, these are only aliases, which appear to point right back to themselves when I do a “Get Info”.Īside from the fact that those are aliases, and not the real files, the big problem is that MAMP PRO does not recognize. It is inside this last folder where the actual key and certificate files are found. This includes a subfolder called “live” in which is another subfolder folder which bears my domain name. As I said, I use MAMP PRO instead.Īfter choosing the actual HTML directory for my domain in my MAMP PRO folder hierarchy – as per instructions I found online – Certbot sucessfully installed and verified all folders and files, which were installed in “/private/etc/letsencrypt”. In other words, I think validation failed the first time around, because Certbot was looking for a running version of OS X’s built-in Apache, server, which I do not use.
Mamp vs mamp pro comparison software#
I have successfully installed Certbot using Homebrew on an iMac running El Capitan 10.11.6.Īfter some initial trouble, I realized that I had to choose “Other” as my web server software – as opposed to choosing “Apache” – because I run my web server using MAMP PRO 4.1, which uses its own proprietary version of Apache.
0 kommentar(er)
