Requests and urllib3 exception
Requests and urllib3 exception: requests.exceptions.ConnectionError
As text you can copy
requests.exceptions.ConnectionError - Kind
- Exception
- Where you meet it
- Raised in your own program by the library
What does requests.exceptions.ConnectionError mean in Requests and urllib3?
Requests describes it as a connection error having occurred. Its quickstart says it is raised in the event of a network problem, such as a DNS failure or a refused connection.
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 request did not complete at the network level. The underlying cause is in the chained exception, often a urllib3 MaxRetryError around a refused connection, a failed name lookup or a reset.
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.ConnectionError?
Read the whole traceback to find the underlying cause. Check the address and the network. If it was raised while waiting on an order request, read open orders and positions before sending it again.
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.