-
Notifications
You must be signed in to change notification settings - Fork 28
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
Error 400 #6
Comments
hello charlyroot, |
Hi mistersms, there is my coin.js :
after one night, the script doesn't make any order... is working for u? |
Hi charlyroot, |
this are my settings: |
i have allways set quantity. |
Only 1 buy/sell this night |
thx for ur coin.js mistersms, I do not think the quantity is blocking since it is automatically put. But what is the "range" mode ? dreKion is it in this mode that the trader has sold / bought this morning? |
it looks like that dreKion is using the range mode, where you can set static sell and buy limits. |
i found out that my installed file trader.js was an older one as the one who was fixed in issue #2 |
was that the problem? |
hi BatmanPDX, i am running pi-hole as internal dns server and in this log, i can only see dns requests to www.binance.com, no requests to stream.binance.com or api.binance.com. |
const coins = [ module.exports = coins; This is mi coins.js |
#########################edit#############################
|
anybody already solved this error? |
Are you running your shell in admin mode? |
yes i am.. but still the same error occurred..did you guys adjusted your "binance_rest.js"? |
i add more logs, please execute and copy the result, thanks |
i have adjusted binance_rest.js and test/orders.test.js >>> question: is this logging know only active in test mode? |
No, the logs are the same in test mode and production mode. New logs prints msg on 400 error |
hi, async openOrders(params = {}){ |
still the same error 400 :
no additionnal log sorry |
@tmalinao you have old version, In the latest version openorders is not available thanks |
@ignaciop000 Thank you bro.. last night i run the bot for the whole night the new version. there is a buy transaction in the dashboard but when i check itself from the binance history nothing is there.. i check my shell i found out that code 400 for the buy also. anyway i will get the updated one and let you know for the result again. |
since the enabled debug in coin.js i had 3 failed buy orders: Symbol: PPTBTC Profit: 0.22 Expected Profit: 0.90 ASK: 0.00176960 BID: 0.00176490 Commission: 0.00050000 profitSelling 0.00178167 does anybody know the reasen for "buy order fail (Not filled)" ? |
now i tried to test with set a stop_loss of 10% for PPTBTC: { after starting the bot there is still a Stop-Loss Amount of 0 shown: should not the 10% stop-loss be seen there? in the webgui there is also no stop-loss of 10% visible: any ideas? |
thx all is working on other order 👍 |
Just for information, if u trade BTC, the lowest order is 0.001. to avoid error 400 : 'Account has insufficient balance for requested action.' 🤣 |
you mean to say if i have only 0.001 then only i can put 1 pair in my coins.js to avoid status code400 in buying? |
yes because if the bot create an order of 1150 BCN for 0.001 BTC for example, is possible the bot want to buy another crypto (ETH for example) before the BCN are received and re-sell. so -> 'Account has insufficient balance for requested action.' |
still i am getting status code 400 |
hello guys any update on this? |
@tmalinao please, share the logs with the detail of 400 error |
hi @ignaciop000 , This is the error i got. |
@mistersms did you manage to fix stop_loss issue? I'm also having same issue, looking for a fix. |
@goodthebest no, i did not manage to fix stop_loss issue. Symbol: PPTBTC Profit: 0.95 Expected Profit: 0.80 ASK: 0.00149990 BID: 0.00148500 Commission: 0.00050000 profitSelling 0.00149762 it looks like the bot is buying and selling at the same time, but stop_loss is set to 0. do you have normal orders for buying and selling? @ignaciop000 attached you can find my logs to status code 400 |
when i open my browser on http://localhost:3001:
npm test:
The text was updated successfully, but these errors were encountered: