Closed jrdn91 closed 5 years ago
It's because Chrome and other browsers doesn't "support" old versions. See: https://www.ssl.com/how-to/turn-off-ssl-3-0-and-tls-1-0-in-your-browser/#CH
Better solution: https://serverfault.com/questions/845766/generating-a-self-signed-cert-with-openssl-that-works-in-chrome-58
I guess README https://github.com/gruntjs/grunt-contrib-connect#support-for-https--http2 should be somehow updated
Duplicate of #193.
I get the privacy error in chrome when trying to load the server. I followed the readme docs for generatice a cert and key and all that and have the settings as such
My livereload settings look like this
I'm using the Yeoman Angular generator, which created this layout.
I've also added both the
server.crt
andca.crt
to my keychain access un thesystem
keychanin, and given them bothAlways Trust
permissions, and restarted Chrome after to make sure.Maybe there is something with the way the connect server is being configured that the yeoman generator is doing a little different than the readme is explaining? Can anyone make sense of this?