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
If a webapp is left idle over night, the websockets typically get closed. When the webapp attempt to send traffic the next day, we should just spin up a fresh channel to the edge router... but something currently goes awry, as shown here:
Uncaught (in promise) TypeError: Can't send data because WebSocket is not opened.
at exports.throwIf (ziti.js:152980)
at ZitiWebSocket.send (ziti.js:153687)
at Object.tlsDataReady (ziti.js:132461)
at Object.tls.flush (ziti.js:74391)
at Object.c.prepare (ziti.js:75013)
at ZitiTLSConnection.prepare (ziti.js:132527)
at ZitiChannel._sendMarshaled (ziti.js:130366)
at ziti.js:130292
at PromiseController._callFn (ziti.js:119945)
at PromiseController.call (ziti.js:119846)
at Messages._createNewMessage (ziti.js:132134)
at Messages.create (ziti.js:132106)
at ZitiChannel.sendMessage (ziti.js:130291)
at ziti.js:129984
The text was updated successfully, but these errors were encountered:
If a webapp is left idle over night, the websockets typically get closed. When the webapp attempt to send traffic the next day, we should just spin up a fresh channel to the edge router... but something currently goes awry, as shown here:
The text was updated successfully, but these errors were encountered: