curl exit code
curl exit code: CURLE_SSL_CONNECT_ERROR (35)
As text you can copy
CURLE_SSL_CONNECT_ERROR (35) - Kind
- Exit code
- Where you meet it
- The exit status of the command
What does CURLE_SSL_CONNECT_ERROR (35) mean in curl?
A problem occurred somewhere in the SSL/TLS handshake. The documentation says to read the error message, because it pinpoints the problem more closely, and that the cause could be certificates, passwords and others. The curl command line tool exits with the same number, which its manual lists under exit codes.
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 to the API could not be set up, so no request was sent. One possible cause is an old version of curl, or of its TLS library, that cannot agree a protocol version with the server.
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 CURLE_SSL_CONNECT_ERROR (35)?
Run the command again with the verbose option and read the message. Update curl. Do not use the insecure option 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.