Only after I remove the SSL version can I connect to the regular version again. On top of all of that, if I create a second copy of my domain in MAMP PRO, and then set it up for SSL – even if those two files are wrong – I cannot connect to the regular HTTP version of my site either. I still cannot connect to the HTTPS version of my server. I made copies of these two files as well, and changed their extensions to “.crt” and “key”, and then set their path in MAMP PRO on the SSL tab for my domain.īut that still does not help. In another folder called “csr”, there is a file called “0000_csr-certbot” and in a folder called “keys” there is another file called “0000_key-certbot”. I am assuming that is because those files are just aliases, and not the real files themselves. MAMP PRO recognizes the files, but I still cannot connect to the HTTPS version of my website, even after I restart MAMP PRO. Then I set the paths to them in MAMP PRO on the SSL tab for my domain. 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 pro 5 ssl software#
Your SSL tab has more information about http/https hosts.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.
#Mamp pro 5 ssl series#
In MAMP PRO 5 a series of digits will be appended to the second host. In MAMP PRO 4 this was done by creating two hosts with the same host name, using the same document root.
You may have created http/https hosts using MAMP PRO 4.
#Mamp pro 5 ssl upgrade#
Click OK to proceed with the database upgrade.Ĭlick on Upgrade to upgrade your databases to 5.7 When you open MAMP PRO and start your servers for the first time you will be prompted to upgrade your database data to MySQL 5.7. If you were using MySQL 5.6 (most likely scenerio) you will be informed of the upgrade to MySQL 5.7.Confirm that all data has been transferred correctly before starting MAMP PRO.Your existing “htdocs” folder will be moved to your new “/Applications/MAMP” folder.You may however keep it, so you can fall back to your original setup. The installer will rename your existing “/Applications/MAMP” to “/Applications/MAMP_current_date”.Double click on the “MAMP_MAMP_PRO_5.xx.pkg” file in your “Downloads” folder to start the installation process.Your old data will be preserved intact in “/Library/Application Support/appsolute/MAMP PRO/db/mysql56”. Your current MySQL data will be copied from “/Library/Application Support/appsolute/MAMP PRO/db/mysql56” to “/Library/Application Support/appsolute/MAMP PRO/db/mysql57”. When upgrading to MAMP PRO 5 you will be asked to upgrade your data to MySQL 5.7.
0 kommentar(er)
