Getting ETIMEDOUT errors, does anyone experience these errors? about binance-trading-bot HOT 10 CLOSED

Sorry, I didn't have time to test in another environment.
I'll close the issue and let you know if I have updates.

from binance-trading-bot.

Sorry for jumping in here, but I have some questions and comments from my usage experience.

1. Where do you get crontab? I have a docker deploy on Linux and never saw there's a configurable crontab.

2. How do you manage to see those errors? There are logs? How do you access them?

I am no expert but Binance have a limit of 1200 API requests per minute, you can see a mention of it in #52 - so even doing 3 request per second you should be good to go.

Maybe it's a issue with the tunnel, have you trying disabling it? Please see #32

from binance-trading-bot.

Hei @chopeta, yes, saw #32 and #52

1. There is no crontab, there is a nodejs module that simulates a cron. You need to change this:
   

   binance-trading-bot/config/default.json

   Line 41 in 4de7391

   "cronTime": "* * * * * *",

   
   and also change in Mongo db -> collection trailing-trade-common -> field cronTime
   and restart

2. The errors are also in logs and on slack.
   docker logs binance-bot | grep ETIMEDOUT

I don't think it is related to the localtunnel, the errors come from calls to binance api. The localtunnel works ok.
Also, I don't think the bot reaches the limit because it just gives a timeout after 2-3 minutes of working ok. If it would reach the limit it would stop working. I think it may be flagged by the ML algorithm but I can't be sure, it may be from my setup. This is why I am asking if someone else encountered this.

Info on Binance limits:
https://www.binance.com/en-AU/support/faq/360004492232

from binance-trading-bot.

@traian13

Hm, doesn't sound like the bot issue. It must be some connection issue between you and Binance API.

Where are you located?

Are you able to run in a cloud server such as DigitalOcean?

from binance-trading-bot.

OK, still a lot to learn here... I didn't have Slack notifs enabled... now I see ETIMEDOUT errors as well inside my Slack channel. Only 3 errors so far, so in theory nothing to be worried about. These are the errors:

• request to https://api.binance.com/api/v3/account?
• request to https://api.binance.com/api/v3/openOrders?
• request to https://api.binance.com/api/v3/account?

From the logs I can't see anything (too many info in there), I guess I have to use bunyan for that.

I also had issues when accessing the bot remotely (over a VPN) using a internet connection with a very high latency... other than that it's working good.

@chrisleekr I am curious about the Slack integration, is there a list of msg types that are defined to be sent to Slack? What else can I expect to see inside Slack?

from binance-trading-bot.

@chrisleekr Thanks for the reply.

I am located in Buchares/Romania.

I didn't run the bot in cloud yet because I am still testing it. But I have to try in another environment.

from binance-trading-bot.

@chopeta

If you enable Slack, you will get notifications such as buy/sell order like below:

from binance-trading-bot.

@traian13 Yeah, please try with another environment (or location).

Timeout is happening when you didn't get the response from API within a specific time.

from binance-trading-bot.

@traian13 if you have no more issue, please close the issue.

from binance-trading-bot.

Sorry, I didn't have time to test in another environment.
I'll close the issue and let you know if I have updates.

Did you find a solution?

I have the same issue...

from binance-trading-bot.