-
Notifications
You must be signed in to change notification settings - Fork 533
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
Message: bitget {"code":"12001","msg":"0PUFFER can be used at most"} #438
Comments
Hi. I never seen this before. Make sure you update FT & NFI and restart the bot first ? |
Also, those trades should have exited completely, no ? Is there an issue with the exit in some way, in general ? |
Yes absolutely, first used official Freqtrade from docker hub follow other coin examples:
Moreover forcing exit from freqtrade UI doesn't works... the coin reimain in the spot market. tryed with "Forceexit limit", "Forceexit market", "Forceexit partial", none of these works. The only way to sell the coin is from Exchange it self, so I must monitor the log freqtrade bot for that messages and sell by hand the problematic pairs. I think this is a problem with Bitget Exchange, because other pairs doesn't have these problems. I also opened the same issue in the freqtrade project issue traking follow open/closed trades screenshot and PUFFER/USDT buy history Not tryed same pairs with other strategy at moment, anyway I don't think this is a NostalgiaForInfinity issue. Thank You for the feedback |
Yes, it's exchange connection API issue. You checked your settings, what you allow through your API key ? |
Yes just verified, the API key have Read-write permissions on:
After freqtrade restart, if I try to force exit by hand of the BOME trade, I get the following exception in freqtrade logs:
Follow the full log:
|
Try to make a new API, maybe ? And use it. |
Hi, I'm running some tests, and it seems (for now) that this error occurs due to an interaction between the Elite Trader function of Bitget and certain altcoins. Now in the Elite Trader section of Bitget, I have disabled many less popular coins, and since making this change, I have not received any more API 12001 errors when trading. It's too early to draw conclusions, but I will update you once I've conducted more tests. For now, however, it seems to be a Bitget issue related to how it handles sell orders. Thank you for the support |
Hi I'm having the same issue, could you post the list of pairs you have disabled please? |
Hi, now I can report that this problem occurs with some pairs but only if Elite Trader is enabled on Bitget. However, I confirm that by deactivating as elite trader, or by deactivating the associated pairs, this problem disappears. Thanks |
Thanks for the quick reply :D. Ive disabled Elite Trader mode. Was hoping to get the best of both worlds but if its not going to work it is what it is. Might just be a case of waiting for bitget to sort their API out. |
Hi,
I'm experiencing an issue with some pairs (bitget exchange):
follow a brief of freqtrade log:
why if the pair is PUFFER/USDT bitget complain about 0PUFFER ? is a ccxt/bitget problem?
how I exclude the problematic pairs from the trading list? (It seems to only happen with new listed pairs and place sell orders)
this is another pair: LUCE/USDT
Thank you for the support
Kind Regards
The text was updated successfully, but these errors were encountered: