Johan Petersson

Any updates on this issue?

One convenient way of getting rid of the warning screen is to enable this flag in the browser settings `chrome://flags/#allow-insecure-localhost`. But the certificate is still invalid and hot-reloading doesn't work.

So there is no way that the automatically created certificates can be generated with a trusted root CA, that we need to trust beforehand somehow? For example IIS Express prompts...

Yes it manifests itself in the browser, but the root cause is that the certificates are not generated with trusted root CA.

@johnpmitsch made no difference. Thanks for the suggestion. The generated certificate still lacks a trusted CA.

Unfortunately I lack the competence, otherwise I would happily contribute. It seems like this is "by design". So maybe this is more of a feature request. But it's kinda weird...

@alexander-akait I will try running the app on different host. Thanks for the suggestion. I however don't see how this will change the generation of the certificate.

> I guess you are asking if there is a way to create the cert signed by a CA cert to and allow users trust that CA certificate as a...

@Enchiridion that seems like an OK workaround. But I'd like to get away of first having to generate a root CA, because if you have to do that, then why...

I used the Office add-in @creage posted. Worked like a charm and gives you a trusted cert. But I don't know how to incorporate that into Webpack.