search

FungY911 / better-grass

Unofficial repository to run grass on VPS. Let's make a better grass world.
58 stars 30 forks source link

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

Open emirhnkoc opened 8 months ago

emirhnkoc commented 8 months ago 
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 8 months ago

Duplaticate of https://github.com/FungY911/better-grass/issues/13#issuecomment-2008955360