-
-
Notifications
You must be signed in to change notification settings - Fork 772
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Binance.us errors out websocket connection #2740
Comments
Hello @KhryptorGraphics, |
BTC/USDC, BTC/USDT, DOGE/BTC, DOGE/USDT, ETH/BTC, ETH/USDC, ETH/USDT, LTC/BTC, LTC/USDT, MATIC/BTC, MATIC/ETH, MATIC/USDT, RENDER/USDT, SHIB/USDT, XEC/USDT was the currencies. It seems to be working now though. I changed nothing. I have another issue though, i will start another thread. |
i actually know this riddle with binance.us (before georgia basically banned binance.us)... it has to do with your api polling time. when dealing with one or two pairs, its ok. BUT, when pulling a bunch of pairs, it hammers the api url and i think binance sees it as a flood, and itll throttle your access. had this problem with freqtrade, it was easier to adjust the api query times in freqtrade... but i cant find it in the binance.us exchange plugin, right now. but in freqtrade you just played around with the api polling times, that way it wouldn't be seen like your "hammering" the api for data. frequi/src/shared/apiService.ts either way i reduced the pairs i watched, it went away... and coinbase (which is legal in georgia, go figure) doesnt have this issue, but then again, yes im back to trading two pairs. BUT, the main suggestion i would say to try is pick two pairs and see if it goes away, then gradually increase. also it might have went away, because it polled the data over a day, working through the pairs. |
Binance.us does not seem to be using websockets correctly.
2024-09-02 16:07:34,331 ERROR ConfigurationWebInterfaceModel Error when checking binanceus exchange credentials: binanceus 418 I'm a teapot {"code":-1003,"msg":"Way too much request weight used; IP banned until 1725311678994. Please use WebSocket Streams for live updates to avoid bans."} (error: DDoSProtection)
The text was updated successfully, but these errors were encountered: