How to resolve errors in your browser console related to WebSockets
Sometimes you may come across errors in your browser’s console, that relates to websockets. Resolution will depend upon underlying cause suggested by the “ <error response>” in the logged error message. Below is a list of possible error responses and possible resolution
Error during WebSocket handshake: Unexpected response code: 403
Above error message suggest that although Clinicea server is reachable but it is unable to allow websocket connection, due to following possible causes:
Session token provided by is not valid or expired. Just sign out and sign back in to Clinicea
Error during WebSocket handshake: Unexpected response code: 302
Above error message suggest that Websocket upgrade request reached Clinicea server but was not processed as a websocket connection request. Instead it was processed as HTTP GET request caused by following:
A Firewall or a proxy server has removed http headers defining request as websocket upgrade request.
Error during WebSocket handshake: Unexpected response code: 500
Above error suggests that an error occurred while websocket upgrade request was being processed. It is usually caused by SSL layer issue. It is rare, if it happens repeatedly, contact Clinicea Support and will have a look at the computer in question.
Error during WebSocket handshake: net::ERR_CONNECTION_RESET
Issue is caused when Firewall is blocking websocket connection, or not configured to handle websocket connection.
Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
Issue is caused by loss of DNS server. This issue is seen when Client is using unstable network connection. If Site is available on internet, It is also worth configuring Client device / Browser to use an external DNS server such as 126.96.36.199 to rule out issue with local DNS server.
Error in connection establishment: net::ERR_NETWORK_CHANGED
This issue is caused by loss of network connection while call is being setup. It could be walking out of wi-fi range or switching between network during the call. It can also be caused by momentary loss of network during the call. Issue may correct itself once network stability is achieved.