Requests and urllib3 exception
Requests and urllib3 exception: urllib3.exceptions.MaxRetryError
As text you can copy
urllib3.exceptions.MaxRetryError - Kind
- Exception
- Where you meet it
- Raised in your own program by the library
What does urllib3.exceptions.MaxRetryError mean in Requests and urllib3?
Raised when the maximum number of retries is exceeded. It carries the connection pool, the URL requested and the underlying error as its reason.
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
urllib3, the library underneath Requests, gave up after the attempts it was allowed. The underlying error it carries is the real failure, such as a refused connection or a failed name lookup.
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 urllib3.exceptions.MaxRetryError?
Read the underlying error it carries and act on that. The retry count is rarely the thing to change.
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.