A websocket proxy written in GoLang, that caches the endpoints: klines, depth, ticker/24hr, and exchangeInfo. It resembles the Binance API behaviour. And has a primary usecase to eliminate ratelimits when querying the Binance API from a single IP.
MIT License
119
stars
32
forks
source link
binance-proxy keeps getting banned by binance every time it starts #8
I'm using binance-proxy 1.2.4 as a proxy for 3 freqtrade bots that run on a lot of pairs on multiple timeframes on futures.
When I restart binance-proxy, I get banned by binance. There's no direct link between the bots and binance, they all go through binance-proxy.
time="2022-08-15T08:19:57Z" level=error msg="FUTURES C98USDT@5m kline initialization via REST failed
error: code=-1003, msg=Way too many requests; IP() banned until 16605565089
Please use the websocket for live updates to avoid bans.."
I have no ideea why binance-proxy would get banned as I think it's its responsibility to ratelimit the queries.
I'm using binance-proxy 1.2.4 as a proxy for 3 freqtrade bots that run on a lot of pairs on multiple timeframes on futures. When I restart binance-proxy, I get banned by binance. There's no direct link between the bots and binance, they all go through binance-proxy.
time="2022-08-15T08:19:57Z" level=error msg="FUTURES C98USDT@5m kline initialization via REST failed error: code=-1003, msg=Way too many requests; IP() banned until 16605565089
Please use the websocket for live updates to avoid bans.."
I have no ideea why binance-proxy would get banned as I think it's its responsibility to ratelimit the queries.