question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Local HTTPS server not working properly.

See original GitHub issue

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): image

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

  System:
    OS: macOS 10.15.2
    CPU: (4) x64 Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.12.0 - /usr/local/bin/node
    npm: 6.11.3 - /usr/local/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    gatsby: ^2.19.7 => 2.19.7 
    gatsby-image: ^2.2.39 => 2.2.39 
    gatsby-plugin-manifest: ^2.2.39 => 2.2.39 
    gatsby-plugin-offline: ^3.0.32 => 3.0.32 
    gatsby-plugin-react-helmet: ^3.1.21 => 3.1.21 
    gatsby-plugin-sharp: ^2.4.3 => 2.4.3 
    gatsby-source-filesystem: ^2.1.46 => 2.1.46 
    gatsby-transformer-sharp: ^2.3.13 => 2.3.13 
  npmGlobalPackages:
    gatsby-cli: 2.8.28

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:14 (10 by maintainers)

github_iconTop GitHub Comments

1reaction
Js-Brechtcommented, Jan 29, 2020

Hello @metalandcoffee,

Can you try something for me? The dev certificates should be stored at ~/Library/Application Support/devcert. If that folder exists, please delete it, then go into your Keychain and remove the devcert certificate authority. After that, run gatsby develop --https again.

There may be other issues, especially running on Mac with the current version of the package devcert that Gatsby uses. #18703 addresses those issues, but that PR’s been waiting to be merged for some time.

0reactions
Js-Brechtcommented, Jan 29, 2020

Closing this because the issue is tracked by #14990, and fixed by #18703

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to use HTTPS for local development - web.dev
If you open your locally running site in your browser using HTTPS, your browser will check the certificate of your local development server....
Read more >
Why is SSL/HTTPS not working on my site? - Support | one.com
There can be several reasons why SSL/HTTPS is not working on your site. ... If your domain is not using our name servers,...
Read more >
How to get HTTPS working on your local development ...
Create a new OpenSSL configuration file server.csr.cnf so you can import these settings when creating a certificate instead of entering them on ...
Read more >
8 Ways to Fix SSL Connection Errors on Various Browsers ...
Adjust your local time and date settings (check the Google Chrome section above for instructions). · Clear your browser's cache and cookies.
Read more >
Troubleshooting SSL related issues (Server Certificate)
The default port for https is 443. I am under the assumption the reader is well-versed in SSL Handshake and the Server Authentication...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found