suddenly started getting websocket 1006 error after months - looks like binance is closing the socket

Websocket
,
1

Hi,
suddenly getting websocket disconnects with error code 1006. The code was working fine for months, and I am continuing to use same library (websockets) to get data from 3 other exchanges.

This is the error :
socket recv exception : code = 1006 (connection closed abnormally [internal]), no reason

If i turn on debug logging the websockets library logs the below lines write before the above error which tells me binance is closing the socket not me any ideas ?

2022-01-17 17:02:03,911,MainThread,DEBUG,client - event = eof_received(),protocol.py,1428
2022-01-17 17:02:03,911,MainThread,DEBUG,client - event = connection_lost(None),protocol.py,1354
2022-01-17 17:02:03,911,MainThread,DEBUG,client - state = CLOSED,protocol.py,1356
2022-01-17 17:02:03,911,MainThread,DEBUG,client x code = 1006, reason = [no reason],protocol.py,1361
2022-01-17 17:02:03,912,MainThread,DEBUG,client - aborted pending ping: 2c9de6d2,protocol.py,1320

2

this just happens from time to time for various reasons and the reason was not necessarily due to Binance. Catch the error and restart the websocket.

3

thanks yes I am catching and getting another websocket connection (plus re-requesting snapshot) but it’s just suddenly happening way more than ever before. I don’t think it’s my connectivity because i have 3 other exchanges with websocket connections and no problems. I increased ping rate to once every 10 secs from 20, i dont think that had any effect.