Log errors

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 […]

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

For some strategies the SamePosition parameter is used (place subsequent orders in the direction of the open position), if SamePosition=YES and, for example, a long position was opened, then subsequent orders will also be placed in long position, but if you try to place orders in short position MoonBot will reject this action and indicate

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

In the MoonBot terminal, open the Settings – Telegram tab. Check “Listen multiple channels” and uncheck “Buy if more than then 1 channel post”.

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.

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

There are several reasons why a signature may be invalid:– The secret key is not set– The secret key does not match the API key– The parameter passed to the server has no value.The error /api/v3/order?orderId=&timestamp=xxxxx&signature=xxxxx can be as follows– The timestamp and signature (in this order) are not specified as the last parameters/sapi/v1/sub-account/status?email=xxx&recvWindow=10000&timestamp=xxx&signature=xxx– The

This log entry indicates that your server is not powerful enough to handle all the strategies running on it in the MoonBot terminal. In addition, you should check the load on your server, which are created by other applications with parallel processes, maybe they also take up a lot of resources on a dedicated server

If the Binance exchange suddenly changed the leverage on a coin, the MoonBot terminal will immediately display an entry like: Exceeded the maximum allowable position at current leverage and after this error will be unscheduled rechecking of limits and adjusting the leverage to them, according to your settings. Without such an error, MoonBot terminal makes