@jsha, I have stated several times now -- in this thread, and in previous related threads -- that changing the file extension of the actual symlinks does NOT help. MAMP PRO still does not recognize the symlinks.
In my previous response to you above, I specifically said near the end:
Even if I go into the "live/www.billkochman.com" folder and rename the symlinks with the .crt and .key file extensions, instead of .pem, MAMP PRO still will not recognize them. While I can click on and select the files if I do the above, the "choose" button is grayed out. So it is still a no-go.
I have also mentioned before that I have ALREADY written to Appsolute -- MAMP PRO developers -- about this on Februrary 10th, and explained the problem very clearly to them. I have even asked them directly why MAMP PRO does not recognize the .pem file extensions. They have yet to give me a clear answer regarding this issue.
Also, I have mentioned before that I am using the very latest version of MAMP PRO, which currently stands at 4.1.1. I always endeavor to keep all of my software up-to-date due to bug fixes, potential vulnerabilities, etc.
I will write to Appsolute again and ask them . . . although to be honest, it might even be better if you write to them developer-to-developer, as it will put more impetus behind the drive to find a solution to this nagging problem.
You can write to them at support@appsolute.zendesk.com
Following is part of my message to Appsolute on February 10th:
----- Begin Quote -----
This is a little long, but I wanted to provide you with all of the details, so that you can more easily help me to figure out what I am doing wrong.
I am trying to use official key and certificate files with my MAMP PRO server, because Google, Mozilla -- and probably others -- don't recognize self-signed certificates. They issue warnings to the web browser user.
After conducting some online research, I discovered "Let's Encrypt" and "Certbot".
Using Homebrew, I figured out how to successfully install Certbot on my iMac.
As it turns out, I discovered that you have to choose the "Other" web server option for MAMP PRO, because if you choose the "Apache" option, when Certbot attempts to verify the installation, it looks for a running version of OS X's built-in Apache server, and not for MAMP PRO.
Anyway, once I chose "Other", and pointed Certbot to the HTML directory for my domain in MAMP/htdocs/My-Domain, it successfully installed all of the required folders and files in "/private/etc/letsencrypt".
This includes a subfolder called "live" in which is another folder which bears my domain name. It is inside this last folder where the actual key and certificate files are found. These files are the following:
privkey.pem
fullchain.pem
chain.pem
cert.pem
However, here is the problem: Not only are the files in that folder just aliases, but they are in the CA standard format of ".pem".
Following instructions I found online, I made a second copy of my domain in MAMP PRO, in which I enabled SSL.
But the problem is that MAMP PRO does not recognize .pem files.
So I made copies of the "privkey.pem" and "fullchain.pem" files, and changed the file extensions to ".key" and ".crt". Then I set the paths to them in MAMP PRO on the SSL tab for my domain.
MAMP PRO recognizes the files . . .
----- End Quote -----
Three days later on February 13th, they responded with this:
----- Begin Quote -----
This may be a problem with MAMP PRO. I know we are going to make some changes how we make http and https work.
At this time you need to make a http and https host with the same name. Our new change will be a check box to add a ssl site. This is a few weeks away.
I will ask our developers how to do this now, if it is possible. It will take a few days to get back to you.
----- End Quote -----
In my response to their above message, on February 13th I reiterated the problem with pem files by saying this:
----- Begin Quote -----
One thing I do agree must be fixed, is the fact that MAMP PRO does not currently recognise the .pem key and certificate symbolic links/aliases in the “lets encrypt” “live” folder.
This is why I had to go into the actual “archive” folder, and make copies of them, change the file extensions to .crt and .key, and place them in their own “mamp” folder under “lets encrypt”. That is the only way that MAMP PRO will recognise them.
----- End Quote -----
So, as you can see, I have more than clearly conveyed to them the problem MAMP PRO has with pem files.
Just now, I wrote to them again, in order to remind them that I am still waiting for a solution to this problem. Here is what I wrote to them:
----- Begin Quote -----
Hello,
I have not heard from you in ten days.
I have been in contact with several technicians from Let’s Encrypt. They are the people who issued me my certificate and key files, which I am now using with MAMP PRO 4.1.1.
They also do not understand why MAMP PRO does not recognize the .pem symbolic links in the “live” folder as valid files, and why MAMP PRO does not allow me to select them.
Like myself, they are wondering what progress you have made towards resolving this issue with the .pem files.
If you would like to join in the discussion directly in the Let’s Encrypt forum, please go here:
Please let me know if you have made any progress towards resolving the .pem file issue, and how soon MAMP PRO users can expect a solution to this problem.
Thank you very much.
Kind regards,
Bill Kochman
----- End Quote -----