WebSocket is already in CLOSING or CLOSED state.

[chfeizy]

Note: for support questions, please use one of these channels: stackoverflow or slack

You want to:

• report a bug
• request a feature

After a while, it will reconnect

chrome 68.0.3440.106

[chfeizy]

engine:socket packet +25s
engine:socket got ping +0ms
engine:socket sending packet "pong" (undefined) +0ms
engine:socket flushing buffer to transport +0ms
engine:ws writing "3" +0ms
engine:ws closing +5s
socket.io:client client close with reason ping timeout +1m
socket.io:socket closing socket - reason ping timeout +1m

[chfeizy]

set pingTimeout: 60000 solve

[crobinson42]

This is related to #3259 and the work around is changing pingTimeout on the server - appears to be an issue with Chrome