#CREATE WEBSITE LOCALHOST FREE#
#CREATE WEBSITE LOCALHOST MAC#

Your certificate should look something like this inside Keychain Access if you’ve correctly followed the instructions till now. Double click the imported certificate and change the “When using this certificate:” dropdown to Always Trust in the Trust section. Once there, import the rootCA.pem using File > Import Items.

#CREATE WEBSITE LOCALHOST MAC#

Open Keychain Access on your Mac and go to the Certificates category in your System keychain.

You need to to tell your Mac to trust your root certificate so all individual certificates issued by it are also trusted. openssl req -x509 -new -nodes -key rootCA.key -sha256 -days 1024 -out rootCA.pem Step 2: Trust the root SSL certificateīefore you can use the newly created Root SSL certificate to start issuing domain certificates, there’s one more step. You’ll also be prompted for other optional information.

#CREATE WEBSITE LOCALHOST FREE#

Feel free to change it to any number of days you want. This certificate will have a validity of 1,024 days. You can use the key you generated to create a new Root SSL certificate. openssl genrsa -des3 -out rootCA.key 2048 You will be prompted for a pass phrase which you’ll need to enter each time you use this particular key to generate a certificate. This file will be used as the key to generate the Root SSL certificate. Generate a RSA-2048 key and save it to a file rootCA.key. If you aren’t familiar with the SSL ecosystem, this article from DNSimple does a good job of introducing Root SSL certificates. This root certificate can then be used to sign any number of certificates you might generate for individual domains. The first step is to create a Root Secure Sockets Layer (SSL) certificate. We’ll be using OpenSSL to generate all of our certificates.

Not anymore.Īfter a ton of Googling, I discovered that the reason for my local certificate getting rejected was that Chrome had deprecated support for commonName matching in certificates, in effect, requiring a subjectAltName since January 2017. The problemĪll the detailed instructions I had found were correct for the time they were written. Chrome always threw a NET::ERR_CERT_COMMON_NAME_INVALID error at me. None of these instructions seemed to work even after I followed them religiously. I ran into a situation where my local development environment’s requests to the server started getting rejected.Ī quick Google search later, I found several articles like this, this or this one with detailed instructions on how I could implement HTTPS on localhost. This poses a problem for developers who use a local development environment because all of them run on out-of-the-box.Īt the startup I’m a part of, we decided to secure our AWS Elastic Load Balancer endpoints with HTTPS as part of a move to enhance security. Securing your server with HTTPS also means that you can’t send requests to this server from one that isn’t protected by HTTPS. Almost any website you visit today is protected by HTTPS.

Create website localhost