Socket.io: WebSocket is already in CLOSING or CLOSED state.

Created on 14 Aug 2018  ·  3Comments  ·  Source: socketio/socket.io

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

You want to:

  • [x] report a bug
  • [ ] request a feature

image
After a while, it will reconnect

chrome 68.0.3440.106

picture chfeizy

All 3 comments

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 picture chfeizy on 14 Aug 2018

set pingTimeout: 60000 solve

chfeizy picture chfeizy on 14 Aug 2018
👎2 👍1

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

crobinson42 picture crobinson42 on 19 Mar 2019
👍1
Was this page helpful?
0 / 5 - 0 ratings

Related issues

thebinarypenguin picture thebinarypenguin  ·  4Comments
gCurtisCT picture gCurtisCT  ·  4Comments
dmuth picture dmuth  ·  3Comments
renkei picture renkei  ·  4Comments
doughsay picture doughsay  ·  4Comments