Local HTTPS server not working properly. #20991
Comments
|
I couldn't reproduce this, so it is probably something specific to your environment. Can you post a full output of |
vladar
added
status: needs more info
|
Hello @metalandcoffee, Can you try something for me? The dev certificates should be stored at There may be other issues, especially running on Mac with the current version of the package |
|
Oh, correction. That's the new folder for development certificates. The old folder is |
|
Hey @vladar and @Js-Brecht! I went ahead and deleted the folder at |
|
I think you need to trust the certificate authority manually, since it looks like you don't have |
|
Unless, of course, you followed the Firefox prompts. Sometimes I forget that not everything shows up in your console 😆. Can you locate your localhost certificate under |
|
I'm not entirely sure about which And then here is the output from running |
|
Can you please post the output for It does seem strange that it would give you a "REVOKED" message, especially after recreating all of the certs. I do know that MacOS will reject a certificate if its expiration date is more than 825 days, but I don't know if that applies to Chrome on Mac, though. You could try running this from your project root: sed -i 's/7000/825/' ./node_modules/devcert-san/dist/root-authority.js
# This command should yield no output, otherwise there was some issue with the sed command
cat ./node_modules/devcert-san/dist/root-authority.js |grep 7000Then clear your |
|
I'm having issues with the Here is the output for |
|
Okay, MacOS apparently uses an old BSD version of 25: utils_1.openssl(`req -config ${constants_1.opensslConfPath} -key ${constants_1.rootKeyPath} -out ${constants_1.rootCertPath} -new -subj "/CN=devcert" -x509 -days 7000 -extensions v3_ca`);Also, I think you'll have to change 59: utils_1.openssl(`ca -config ${constants_1.opensslConfPath} -in ${csrFile} -out ${certPath} -outdir ${constants_1.caCertsDir} -keyfile ${constants_1.rootKeyPath} -cert ${constants_1.rootCertPath} -notext -md sha256 -days 7000 -batch -extensions server_cert`); |
|
Aha... I dug up an old issue in the The only issue with changing the source like I've suggested is that it'll be replaced any time you update your |
|
Omgosh. You fixed it @Js-Brecht!!!! Things work perfectly now. But I'm going to go through the information you linked above to look into creating my own custom certificate. Thanks so much for taking the time out to help me! You're a gem. |
|
You're welcome. Glad I could help 🙂 |
Description
When following the instructions in the Gatsby docs to use a Local HTTPS server during development, the process seems unsuccessful.
When I go to https://localhost:8000/, it shows the following privary error (Chrome):
Steps to reproduce
Follow the instructions in the link above.
Expected result
The https://localhost:8000/ URL should take me to my Gatsby site.
Actual result
See above screenshot.
Environment
The text was updated successfully, but these errors were encountered: