-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update self signed ssl certificates #436
Conversation
Thanks |
Thanks for this great fix, is this released? |
I just upgraded to these versions
and am now getting the same error as @wbobeirne |
@wwselleck it looks like you're using the old certificate, likely meaning you're on a version of webpack-dev-server that hasn't been updated since March 24th. The current stable version on npm (1.14.1) has the old cert. |
@wbobeirne Refresh, I updated and got the same error as you 😄 |
Is there a definitive solution for this? What is the earliest version that has the new certificate? |
I was able to get past the "This certificate has not been verified..." error by just proceeding anyway on Chrome, and adding a security exception on Firefox, once I got to the red lock screen. After that calls to the webpack dev server were going through. |
I have another project that enforces HSTS so proceeding only works as long as I don't visit the other site. That doesn't work well when I'm trying to implement SSO D: |
Got this working via pointing the key, cert and ca to the correct files.
Then adding the certificate to my Keychain Access and trusting the certificate. Hope this helps.
|
This should resolve issue #340.
The new certificate will expire in 5 years (Thursday 24 March 2021).
I believe most of the data is the same, but I have added localhost as a Common Name so that Chrome will accept it.