WebSocket close code
WebSocket close code: 1015 TLS handshake
As text you can copy
1015 TLS handshake- Kind
- Close code
- Where you meet it
- When a WebSocket connection closes
What does 1015 TLS handshake mean in WebSocket?
A reserved value that is never sent in a close frame. It is for a program to report that the connection was closed because the TLS handshake failed, for example because the server's certificate could not be verified.
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 secure connection underneath the WebSocket could not be set up, so no stream was ever opened.
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 1015 TLS handshake?
Check the address and that it starts with wss. Check the computer's clock and its store of root certificates. Do not switch certificate checking off to get past it.
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.