All geek questions in one place

Secured WebSocket does not work in Chrome58

I upgraded my Chrome to 58 and found that the protected WebSocket is no longer working, showing the console (WebSocket connection to 'wss: //127.0.0.1: 1234 /' failed: error in establishing connection: net :: ERR_INSECURE_RESPONSE), I know that Google does not approve the SHA1 certificate, so it created a new self-signed certificate with SHA256, but it still does not work, so the self-signed certificate is not allowed in this scenario? (I am using the "new WebSocket (" wss: //127.0.0.1: 1234 ")")

+4
source share
2 answers

It turns out that the certificate must have subjectAltName with "IP = 127.0.0.1" for my certificate to work in Chrome58, not sure if this is a Chrome bug or a new requirement

+6
source

Edit: See @Edgar answer. subjectAltNameseems to have become a requirement for self-signed certificates with Chrome 58.

It seems that the OP has also addressed this issue in the Google Help Community . Response from the Google Help community:

"I see that you are using Chrome Beta, which is an experimental version of Chrome that is testing new features. I would recommend using Chrome Stable, which received full testing and is an updated version. To avoid crashes and other problems."

. wss://localhost Chrome 59 (Canary/Beta) .

. , - Chromium #378566 - . , wss:// , . Chrome 59 (Canary/Beta), .

+1

Source: https://habr.com/ru/post/1673331/

More articles:


All Articles