You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2024-12-29T17:05:03.236Z UniFi-Error:SharedProtectWebSocket connect(): this.ws.on(error: Error: Unexpected server response: 200
at ClientRequest.<anonymous> (/data/node_modules/node-red-contrib-unifi-os/node_modules/ws/lib/websocket.js:913:7)
at ClientRequest.emit (node:events:518:28)
at HTTPParser.parserOnIncomingClient (node:_http_client:702:27)
at HTTPParser.parserOnHeadersComplete (node:_http_common:118:17)
at TLSSocket.socketOnData (node:_http_client:544:22)
at TLSSocket.emit (node:events:518:28)
at addChunk (node:internal/streams/readable:561:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
at Readable.push (node:internal/streams/readable:392:5)
at TLSWrap.onStreamRead (node:internal/stream_base_commons:191:23)
The text was updated successfully, but these errors were encountered:
Getting a 200 response for a web socket is not valid, it should be 101 ... Switching Protocol.
Seems like some strange Protect behaviour 🤷♂️
Have never seen this response for a web socket, so what are you connecting to exactly?
The ws node package (that we use) received something its not supposed to
Unifi have been changing a lot lately, and efforts are now going towards using the official API (web hooks)
2024-12-29T17:05:03.236Z UniFi-Error:SharedProtectWebSocket connect(): this.ws.on(error: Error: Unexpected server response: 200
The text was updated successfully, but these errors were encountered: