Closed PribhuPatel closed 3 years ago
Hello!
I am not sure about your problem, but I THINK that the exception handling is causing this error...
I dont see the output of print(e)
which would be very interesting! Because for example if there is a ProtocollError which maybe doesnt close the connection, it would trigger a reconnect an then you trigger an connectionResetError because there is already an existing connection and you run into an exception loop....
Con A is established and throws an exception without closing Con A. The exception gets catched and opens a new Con B, but there is still Con A, so its closing Con A with a new exception which triggers the creation of Con C, but Con B is still alive ....
You know what i mean? I am not sure but i would investigate into this direction.
Perhaps this isn't the correct place to inquire about this, but if this repo is a fork of python-binance
, this issue may be somewhat related to:
https://github.com/sammchardy/python-binance/issues/389
At least the symptoms are similar in that:
you are not exceeding limit requests, you are not banned, and the script runs fine for a while but fails with a ConnectionError that is hard to handle correctly.
most of the comments in python-binance are regarding to websockets, not the rest api.
so the error is comming from different sources.... (websocket and requests)
@PribhuPatel I am closing this, if you want investigate further, just answer :)
I am trying to make continuous requests to Binance. I am not going out of limit requests(> 1200) per minute. But still getting this error. Even my IP is not banned. After the error I rerun the code, it is working fine for the next 5-6 hours every time. And I am running this on VM. So, it is not the case that my IP is banned and after changing the internet connection my IP is changed.
Here is the full error