Forum Index » Browser development » Secure websocket error 'ERR_SSL_PROTOCOL_ERROR'   XML
 
Author Message
[Post New]24/04/2017 14:21:56
    Subject: Secure websocket error 'ERR_SSL_PROTOCOL_ERROR'
[Up] #1
David10


Joined: 17/04/2018 04:27:59
Messages: 0
Offline
I am running the latest version of JABRA Websocket SDK (1.2.393.0).

Once installed and running I have no problem connecting over insecure websocket, but connecting over wss gives me the following error in Chrome:
WebSocket connection to 'wss://localjabrawebsocketserver:8080/' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR

Firefox and Edge give me similar errors.

Is there something I need to turn on or configure to activate wss?
[Post New]26/04/2017 13:32:29
    Subject:
[Up] #2
Mehmet


Joined: 17/04/2018 04:27:59
Messages: 1
Offline
Hi David,
It seems like Chrome rel 58 exhibits this issue, and we will check if their are any workarounds from here. it seems that IE still works but we have to investigate for the other browser applications.

Stay tuned for an update.

Thanks
Mehmet
[Post New]26/04/2017 14:33:55
    Subject:
[Up] #3
David10


Joined: 17/04/2018 04:27:59
Messages: 0
Offline
I've just checked and this error happens on Chrome 57. Here are the errors I've got from the different browsers:

ie 11.1066.14393.0: SecurityError

firefox 53.0: Firefox can't establish a connection to the server at wss://localjabrawebsocketserver:8080/.

Edge 38.14393.1066.0: SCRIPT12017: WebSocket Error: SECURITY_ERR, Cross zone connection not allowed

Chrome 57.0.2987.133: VM46:35 WebSocket connection to 'wss://localjabrawebsocketserver:8080/' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR--

I'm running Windows 10 pro version 10.0.14393

The service is installed and running. From all browsers I am able to connect to and communicate with the non-secure ws://localjabrawebsocketserver:8080

Could this be a some other issue. Windows blocking the connection? I've checked the firewall and all traffic is allowed to/from the service.
[Post New]02/05/2017 10:21:43
    Subject:
[Up] #4
Mehmet


Joined: 17/04/2018 04:27:59
Messages: 1
Offline
Thanks David for the detailed information. We are currently working on root-cause analysis, one alternative evaluated is if we can 'work-around' issue with a new certificate. I will let you know once we have some material you can evaluate.

Thank you and stay tuned for an update.

/Mehmet
[Post New]09/06/2017 10:41:08
    Subject:
[Up] #5
Mehmet


Joined: 17/04/2018 04:27:59
Messages: 1
Offline
Hi David, our team have identified a work-around for the issue.
Its described here:
http://www.techrepublic.com/article/how-to-resolve-ssl-certificate-warnings-produced-by-the-latest-chrome-update/

Hope you can use this as a temporary solution - until we have a permanent one.

Thanks

/Mehmet
 
 
Go to: