Skip to content
This repository has been archived by the owner on Feb 16, 2020. It is now read-only.

Gekko encountered an error and can't continue [binance.js] Response code 400 #2037

Closed
AndreiGhitan opened this issue Mar 18, 2018 · 12 comments
Closed

Comments

@AndreiGhitan
Copy link

I am getting the following error with the livetrader on binance:

RECEIVED ERROR IN GEKKO 0101215627964186

Gekko encountered an error and can't continue

Gekko encountered an error and can't continue

Error:

[binance.js] Response code 400

Meta debug info:

Gekko version: v0.5.12
Nodejs version: v9.8.0

Since I started it, it did one trade for me meaning it bought the asset with ETH, and minutes later this error popped up and I tried everything, restarted my machine and also followed the instructions to update binance to 1.2.2. Every time now when I strt the live trader it gives me this error.

Can you guys help me get this fixed please?

@bbkilboz
Copy link

Can you check your system clock?
There was a difference between my system clock and binance server clock, on my instance, and when i synced my system clock with NTP it started working again.

@AndreiGhitan
Copy link
Author

I have checked it and it is set on automatic. I am running it on Mac OSX High Sierra.

How do I sync it with NTP on mac?

@bbkilboz
Copy link

If it's automatic then it should be syncing with a NTP server of Apple.
You can try to change its server to another Apple server or 0.pool.ntp.org but I doubt that'll work.
Hope you find a solution soon

@AndreiGhitan
Copy link
Author

AndreiGhitan commented Mar 18, 2018

I followed some of the tips posted in other threads for the solution but it still gives me this error, would be really awesome if somebody could help me get this sorted

@askmike
Copy link
Owner

askmike commented Mar 20, 2018

In what region (in the world) are you based? And do you have a fast internet connection?

@AndreiGhitan
Copy link
Author

AndreiGhitan commented Mar 20, 2018

In Romania, and yes my internet connection is fast and stable.

@JThobbyist
Copy link

I’m also having this problem

@JThobbyist
Copy link

Actually nvm. My issue was because I changed my binance orders from LIMIT to MARKET, and the api didn’t like that I left the other settings unchanged. So for me the fix was to comment-out the time in force and price

@AndreiGhitan
Copy link
Author

I will try running it in windows a bit later and see if it does the same. It kills me though cause I found a killer strategy and can't use it.

Only thing it does is that it buys the asset and never switches back. It just pops that error. Would love to get this running as soon as possible since I really like this bot :)

@AndreiGhitan
Copy link
Author

it’s even worse on windows, as soon as I launched the live trader it popped the error :(

@askmike
Copy link
Owner

askmike commented Apr 1, 2018

Sorry about that, Gekko was not properly printing the actual error, please download the latest develop branch and try again :)

@askmike askmike closed this as completed in 07a4d67 Apr 1, 2018
bagg3rs pushed a commit to bagg3rs/gekko that referenced this issue Apr 25, 2018
@hoppy1969
Copy link

hoppy1969 commented May 6, 2018

I'm getting the same error. I just downloaded the gekko-develop today. Everything seemed to download fine, but if I try to import data or start a new gekko I get the following error: Gekko encountered an error and can't continue. In my command window it looks like this:
Gekko 308934527360494 started
--> POST /api/startGekko 200 11ms 148b
RECEIVED ERROR IN GEKKO 308934527360494

Gekko encountered an error and can't continue

Gekko encountered an error and can't continue

Error:

{}

Meta debug info:

Gekko version: v0.5.14
Nodejs version: v8.11.1

I saw some people talking about time, but mine matches up to the binance clock which is the local time I'm working on here. What am I missing?

I switched browsers to Firefox and this seems to have fixed the issue.
v/r
Hoppy

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants