FungY911/better-grass

[BUG] WebSocket not in appropriate state for liveness check...

Opened this issue · 1 comments

emirhnkoc commented 
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...
FungY911 commented

Duplaticate of #13 (comment)