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
better-grass > 192.168.2.139 [OPEN] Websocket is open
better-grass > 192.168.2.139 [CLOSE] Connection closed, code=1006, reason=
better-grass > 192.168.2.139 [❗] WebSocket does not appear to be live! Restarting the WebSocket connection...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 [OPEN] Websocket is open
better-grass > 192.168.2.139 [CLOSE] Connection closed, code=1006, reason=
better-grass > 192.168.2.139 [❗] WebSocket does not appear to be live! Restarting the WebSocket connection...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 [OPEN] Websocket is open
better-grass > 192.168.2.139 [CLOSE] Connection closed, code=1006, reason=
better-grass > 192.168.2.139 [❗] WebSocket does not appear to be live! Restarting the WebSocket connection...
better-grass > 192.168.2.139 [OPEN] Websocket is open
better-grass > 192.168.2.139 [CLOSE] Connection closed, code=1006, reason=
better-grass > 192.168.2.139 [❗] WebSocket does not appear to be live! Restarting the WebSocket connection...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
better-grass > 192.168.2.139 WebSocket not in appropriate state for liveness check...
The text was updated successfully, but these errors were encountered:
The text was updated successfully, but these errors were encountered: