-
Notifications
You must be signed in to change notification settings - Fork 341
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
Have problem ETIMEDOUT #149
Comments
I use any values: But i have this error. My config
` |
I'm having the same issue anyone have any luck resolving this? |
I was able to resolve my issue it was a firewall issue, was running on a VM and also had to increase my resources. |
@ScuzzyHoulihan How did you solve it? |
Not a problem when using BTC as the main coin. |
At the end I could solve it and I improved the bot, the code and the speed.
Even the algorithm is better and is showing me positive opportunities each
minute. The only problem (not related with the bot at all) is the glide of
the market and sometimes the bot needs to take more than hour to do the
three orders.
|
@yumewebs, can you share your config for USDT and the improvements you made to the bot? |
How?? Share your config pls |
Hello please can you share your config, thanks and I'm waiting for your reply |
Hello i Have problem
ETIMEDOUT
How i can solve this ?
`
oleg@SKY-NOTE:~/projects/trb/binance-triangle-arbitrage$ npm start
Checking configuration ...
Checking latency ...
Experiencing 505 ms of latency
Fetching exchange info ...
Found 1038/1405 currently trading tickers
Found 174 triangular trades
Checking market conditions ...
Opening 321 depth websockets for 321 tickers ...
Error: ETIMEDOUT
at Timeout. (/home/oleg/projects/trb/binance-triangle-arbitrage/node_modules/request/request.js:848:19)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7) {
code: 'ETIMEDOUT',
connect: true
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start:
node src/main/Main.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/oleg/.npm/_logs/2021-04-18T23_14_13_424Z-debug.log
`
The text was updated successfully, but these errors were encountered: