WebSocket close code
WebSocket close code: 1006 Abnormal Closure
As text you can copy
1006 Abnormal Closure- Kind
- Close code
- Where you meet it
- When a WebSocket connection closes
What does 1006 Abnormal Closure mean in WebSocket?
A reserved value that is never sent in a close frame. It is for a program to report that the connection closed abnormally, without a close frame being sent or received.
Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders.
What it means in trading API work
The connection simply dropped: a network fault, an idle timeout somewhere on the path, or the server vanishing. Your library reports 1006 because no close frame arrived, which is also why it comes with no reason text.
This part is this site's own explanation, written for people learning to call a trading API. It is not part of the source cited above and it describes no particular broker.
What should I do about 1006 Abnormal Closure?
Reconnect with growing pauses and subscribe again. Send the heartbeat or ping the API documents, so that an idle connection is not dropped. Expect to have missed updates while disconnected, so read the current state after reconnecting.
This page is an independent explanation in plain words. The definition itself is in the source it was read from, which is the authority if the two ever differ.