Requests and urllib3 exception
Requests and urllib3 exception: requests.exceptions.SSLError
As text you can copy
requests.exceptions.SSLError - Kind
- Exception
- Where you meet it
- Raised in your own program by the library
What does requests.exceptions.SSLError mean in Requests and urllib3?
The Requests guide says the library verifies SSL certificates for HTTPS requests by default and throws SSLError when it is unable to verify one. Its example is a certificate whose host name does not match.
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 verified. Usual causes are out of date root certificates, a wrong system clock, a proxy that signs traffic again with its own certificate, or a wrong host name.
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 requests.exceptions.SSLError?
Update Requests and the root certificates it uses, and check the clock and the host name. Do not pass verify=False: it removes the check that your credentials are going to the real server.
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.