Cannot run locally (Chrome Privacy error)

Description

Hello, I’m excited to be trying out Jitsi! Thanks for this amazing product.

My first task involves running this repo locally. After installing and doing make dev I see the following in Chrome – note that there’s no bypass link given.

I don’t know what the cert it’s referring to might be, it has an expiration date of May 2020 and is not something in my keychain. When I click on the NET::ERR_CERT_INVALID it shows the key preceded by:

Subject: localhost
Issuer: localhost
Expires on: May 2, 2020
Current date: Apr 2, 2020
PEM encoded chain:
...

I tried generating a self-signed cert for localhost (I’m on macos), and setting it to always trust but it always shows this screen.

Note that I have other dev projects that run locally using https without any issue – this is a new one for me!

---

Current behavior

Cannot view https://localhost:8080 despite Webpack working without any problems

./node_modules/.bin/webpack-dev-server
ℹ ｢wds｣: Project is running at https://localhost:8080/
ℹ ｢wds｣: webpack output is served from /libs/
ℹ ｢wds｣: Content not from webpack is served from /Users/moses/Documents/cloudengage/chord-video

---

Expected Behavior

Can view https://localhost:8080

---

Steps to reproduce

• clone repo
• npm install
• make dev (I also tried running make)

---

Environment details

Mac Catalina 10.15.2

[damencho]

In the Chrome address bar, type “chrome://flags/#allow-insecure-localhost“ Select the “Enable” link.

[mosesoak]

Thanks for the info, @damencho, I will! And yes, a docs update on this would be fantastic, if it works out I’ll provide a PR to make this issue worth your time. Thanks again