Log errors

When trading in the MoonBot terminal, no Buy order was placed for the Bybit exchange, but in the log I found an entry like: “Buy order: FAIL; {“retCode”:10001,”retMsg”:”estimated will trigger liq”, what does this mean?

When trading in the MoonBot terminal for the Bybit exchange, if no Buy order has been placed, but there is an entry in the log like: Buy order: FAIL; {“retCode”:10001,”retMsg”:”estimated will trigger liq”, this means that automatic protection has been activated on the Bybit exchange, which prevented an attempt to place a Buy order, the

When trading in the MoonBot terminal, no Buy order was placed for the Bybit exchange, but in the log I found an entry like: “Buy order: FAIL; {“retCode”:10001,”retMsg”:”estimated will trigger liq”, what does this mean? Read More »

When trading in the MoonBot terminal for the Gate exchange, no orders are placed, and the log contains an entry like: “[400] {“label”:”CONTRACT_BONUS_DISABLED”,”message”:”can not put order at contract with bonus disabled while having bonus”}”, how can I fix this?

If no orders are placed in the MoonBot terminal for the Gate exchange, and the log contains an entry like: [400] {“label”:”CONTRACT_BONUS_DISABLED”,”message”:”can not put order at contract with bonus disabled while having bonus”}, which translates as “unable to place an order under the contract with the disabled bonus, if there is a bonus,” then most

When trading in the MoonBot terminal for the Gate exchange, no orders are placed, and the log contains an entry like: “[400] {“label”:”CONTRACT_BONUS_DISABLED”,”message”:”can not put order at contract with bonus disabled while having bonus”}”, how can I fix this? Read More »

I have a terminal MoonBot on the Gate exchange gets up on API errors and in the log there is a record like Set Buy order: FAIL; [400 CONTRACT_IN_DELISTING] how to fix the situation?

Such a log entry indicates that the API has not yet deleted information about a token that has already been removed from the exchange, and MoonBot terminal tries to place an order on the nonexistent token, gives a series of errors and gets protected by the API limit. In the latest version of the MoonBot

I have a terminal MoonBot on the Gate exchange gets up on API errors and in the log there is a record like Set Buy order: FAIL; [400 CONTRACT_IN_DELISTING] how to fix the situation? Read More »

I have both long and short orders set up in the MoonBot terminal, but after placing an order in long position, short orders are not placed and the log shows the following entry: Market XXX is opened in Long position, how can I fix this?

For some strategies in the MoonBot terminal, on the Filters / Price/Position tab of the strategy settings, the SamePosition parameter is used (to place subsequent orders in the direction of the open position). If SamePosition=YES and, for example, a long position has been opened, subsequent orders will also be placed as long orders, and if

I have both long and short orders set up in the MoonBot terminal, but after placing an order in long position, short orders are not placed and the log shows the following entry: Market XXX is opened in Long position, how can I fix this? Read More »

When registering API keys in the MoonBot terminal, the following error appears in the log: AuthCheck error! TryCount=3 Works only with UTA Accounts! (ok) resp: [200], how can I fix it?

Immediately after registering on the Bybit exchange, you need to change your account type to UTA (ETA in the Russian version). You will be prompted to do this when you first log in to your personal account. Then create API keys and register them in the MoonBot terminal. For more information about connecting to the

When registering API keys in the MoonBot terminal, the following error appears in the log: AuthCheck error! TryCount=3 Works only with UTA Accounts! (ok) resp: [200], how can I fix it? Read More »

I saw an entry like:Status: 400 This symbol is not allowed for this account, what does it mean?

An entry in the MoonBot terminal log of the following form: “Status: 400 This symbol is not allowed for this account” means that the account and the symbol do not have the same access rights for trading. This error is not related to MoonBot terminal settings, please contact the exchange’s support team.

I saw an entry like:Status: 400 This symbol is not allowed for this account, what does it mean? Read More »

When trading on MoonBot spot terminal for Bybit exchange, I saw the following entry in the log: USDT-SUI Set Buy order: FAIL; {“retCode”:170241, “retMsg”: “To proceed with trading, users must read through and confirm that they fully understand the project’s risk disclosure document. For App users, please update your Bybit App to version 4.16.0 to process.”, what does this do?

When receiving an entry of the following type: USDT-SUI Set Buy order: FAIL; {“retCode”:170241, “retMsg”: “To proceed with trading, users must read through and confirm that they fully understand the project’s risk disclosure document. For App users, please update your Bybit App to version 4.16.0 to process.” You should go to spot trading in your

When trading on MoonBot spot terminal for Bybit exchange, I saw the following entry in the log: USDT-SUI Set Buy order: FAIL; {“retCode”:170241, “retMsg”: “To proceed with trading, users must read through and confirm that they fully understand the project’s risk disclosure document. For App users, please update your Bybit App to version 4.16.0 to process.”, what does this do? Read More »

In the log I saw entries like: Same IPs; Lets check Google DNS, but I have the fourth connection method, and MoonBot terminal works fine, should I be worried?

This type of log entry signals that there are difficulties in determining the IP servers of Binance exchange on connection methods 2 and 3. When working on a dedicated server, such as Vultr, this should not be the case, if you have this entry on your home computer and if everything works fine, you can

In the log I saw entries like: Same IPs; Lets check Google DNS, but I have the fourth connection method, and MoonBot terminal works fine, should I be worried? Read More »