27

SSL certificates created by MAMP are not working in Chrome. I'm getting a "Not secure" issue.

Is there a workaround for this?

enter image description here

codewithfeeling
  • 6,236
  • 6
  • 41
  • 53
  • Also see [How do you sign Certificate Signing Request with your Certification Authority](http://stackoverflow.com/a/21340898/608639) and [How to create a self-signed certificate with openssl?](http://stackoverflow.com/q/10175812/608639) You will also need to place the self-signed certificate in the appropriate trust store. – jww Jun 17 '17 at 14:52

5 Answers5

57

**NOTE: Since I posted this, Google have acquired the .dev top level domain, so it's not advised to use .dev hostnames for your local development. I use *.dv now. When reading this answer, please replace .dev with .test or something else when recreating the steps in your own project. Use of .local is not advised **

Chrome now requires SSL certificates to use the "Subject Alt Name" (SAN) rather than the old Common Name. This breaks self-signed certs previously generated by MAMP.

Fortunately, the workaround is pretty straightforward.

Here are all the steps from the very first moment of setting a host to be SSL in MAMP Pro. If you previously created SSL certificates in MAMP, then I've found that deleting them and starting again using this method works.

  1. Create your hostname, eg. test.dev and select your document root

  2. Click the SSL tab, and check the "SSL" box. Make sure you leave the other checkbox "Only allow connections using TLS protocols" unchecked.

Screenshot showing SSL panel in MAMP Pro

  1. Click the "Create self signed certificate" button and fill in the popup form with the relevant details. Click "Generate" and save the certificate in /Applications/MAMP/Library/OpenSSL/certs/

Screenshot of SSL certificate creation popup form in MAMP Pro

  1. Save your changes in MAMP, and restart the servers.
  2. Click the round arrow button beside "Certificate file" in the MAMP SSL panel (Show in Finder). Double click the .crt file that is highlighted - it should be named like your host, eg. if your host is test.dev then your certificate file will be test.dev.crt. This should open Keychain Access and you should see the new certificate in there.
  3. Right click / Control click on the certificate, and choose "Get Info". Click the drop-down triangle beside "Trust"

Screenshot of Mac Keychain Access for certificate

  1. From the "When using this certificate" selector, choose "Always Trust" - every selector should change to show "Always Trust". Close that window. It will ask for your Mac OS system password to make that change. You should see that the certificate icon shows a little blue plus sign icon over it, marking it as trusted.

enter image description here

  1. Restart Chrome.
  2. Visit your new hostname, and enjoy the green https in the browser bar.

Screenshot of https working in Chrome

codewithfeeling
  • 6,236
  • 6
  • 41
  • 53
6

I followed the answers. What worked for me was setting the port number to 443 in the general tab

Jadrenko
  • 71
  • 2
  • 8
4

If the solution above doesn't help, go to chrome://flags look for "Allow invalid certificates for resources loaded from localhost" and enable it, restart Chrome and you should be good to go.

Xelance
  • 112
  • 2
  • 1
    Hi, I have tried both adding trusted certificates and adding this flag. I can confirm that both are in place, but this is still not working? – GCien Feb 26 '18 at 09:15
3

For those that are still having issues, try using port 8890. The default MAMP ssl port is 8890 so visit https://test.dev:8890. Worked for me.

Douglas Rogers
  • 398
  • 2
  • 9
1

For me, it wasn't necessary to use MAMP Ports but instead they were kept at Apache defaults. I also didn't need to specify port 443. What did help once I created the self-signed cert was to install the certificate icon that shows in Chrome into my Mac Keychain by dragging the image to the desktop and double-clicking it. Once it's installed into the Mac Keychain, you can set it to trust the cert.

Refer to this illustrated answer: https://www.accuweaver.com/2014/09/19/make-chrome-accept-a-self-signed-certificate-on-osx/

  • MAMP Pro 4.5
  • Chrome 71
PWM
  • 196
  • 2
  • 5