Gunthy
GUNBOT: The automatic profit generator => Technical Support & Development => Topic started by: 125xx on February 29, 2020, 02:33:53 AM
-
Hi! [sorry, I posted this in general originally by accident]
I'm having issues closing positions on binanceFutures.
gunthy-linux Logs look like so - https://pastebin.com/9qFNP1Wx
Config.js - https://pastebin.com/28HXYtwY
It will print its attempts to close positions for hours, but never does.
Is there any way to get better granularity on whats happening here? Can the API calls be traced/logged to a file or the server-side responses?
I'm really struggling and just grabbed an ultimate license... I have to make all position closes manually :(
Appreciate any help!
-
More on this. So I setup a proxy and intercepted the API calls to binance.
When gunbot is attempting to BUY against a SELL [close a short] - it sends: timestamp=1582949894415&recvWindow=5000&symbol=BTCUSDT&quantity=-2&type=LIMIT&side=BUY&newClientOrderId=<clientID>&price=8747.8&timeInForce=GTC&signature=<sig> to https://fapi.binance.com/fapi/v1/order
However, fapi.binance.com is returning:
{
"code": -1102,
"msg": "Mandatory parameter '-2' was not sent, was empty/null, or malformed."
}
Thus, the position isn't being closed.
Why is this? Is this a bug or a setting I need to tweak to ensure this param is passed?
-
Why don't you ask your reseller to add you to the Official Gunthy Elite Channel on Telegram, I'm sure you have a better chance to get help there if you post your issue.
Hope it Helps.
-
It was known issue. It's fixed on latest Gunbot version:
https://gunbot.shop/gunbot-v18-3-9-download/