Log errors

In the log I saw records of the following form: Set Buy order: FAIL; Status: 400 Limit price can’t be higher than, but I don’t have orders placed, what kind of error is this?

If you have such an error in your logs and orders are not placed, it means that the exchange does not allow you to set an order higher than your strategy wants. For example, you have the following entries in your log: 1) Task 342 started; USDT-XVS (strategy ) UseAsk: 7.9260 CurAsk: 7.92360 BUY 10.405 […]

In the log I saw records of the following form: Set Buy order: FAIL; Status: 400 Limit price can’t be higher than, but I don’t have orders placed, what kind of error is this? Read More »

I have seen in the log the following entries: AutoStart: FALSE PumpQ<0! and no orders are placed, what does it mean and how to correct the error?

In the MoonBot terminal, go to the Settings – Main tab and uncheck the boxes in the “Good pump” and “Risk limit conditions” sections. These are old settings that are no longer applicable.

I have seen in the log the following entries: AutoStart: FALSE PumpQ<0! and no orders are placed, what does it mean and how to correct the error? Read More »

In the log I saw a record of the following form: API Errors level increased, but the orders are not placed, what does it mean and how to correct the error?

MoonBot terminal registers an increased level of API errors, which may appear due to lags with the exchange, problems with the Internet, general problems in communicating with the exchange and triggers protection by API. Enabling this protection is located on the tab Settings – Autostart, if the checkbox is set at the parameter “Auto Stop

In the log I saw a record of the following form: API Errors level increased, but the orders are not placed, what does it mean and how to correct the error? Read More »

When I try to run Telegram in the bot, it gives the following error: Built-in Telegram: Auth status: error { code = 400 and at the same time, Telegram does not unlog into the MoonBot terminal. How to fix it?

You need to close any unnecessary devices connected to this Telegram account, then close the MoonBot terminal and delete the entire tdlib folder. After that, load the MoonBot terminal in administrator mode and perform the procedure to connect to Telegram again on the Settings – Telegram tab.

When I try to run Telegram in the bot, it gives the following error: Built-in Telegram: Auth status: error { code = 400 and at the same time, Telegram does not unlog into the MoonBot terminal. How to fix it? Read More »

I saw in the log a record like: New Order won’t proceed due to API or CPU overload and no orders are placed, what does it mean and how to fix it?

This message most often appears in the log of the MoonBot terminal, which is installed on a dedicated server, and it reports that there is an API or CPU (processor) overload. To fix this kind of error you need to: <br /> 1) Go to Menu-System Setting and check “VDS optimized mode”. <br /> 2)

I saw in the log a record like: New Order won’t proceed due to API or CPU overload and no orders are placed, what does it mean and how to fix it? Read More »

In the log I saw records of the following form: Status: 401 Invalid API key, IP, or permissions for action and at the same time orders are not placed, what does it mean and how to fix the error?

If you find information in the log about errors like: <br /> – API key format invalid <br /> – Status: 401 Invalid API-key, IP, or permissions for action <br /> – Haven’t found buy orders, waiting <br /> If you have stopped placing orders, this means that the exchange Binance has disabled checkboxes for

In the log I saw records of the following form: Status: 401 Invalid API key, IP, or permissions for action and at the same time orders are not placed, what does it mean and how to fix the error? Read More »

In the log I saw entries like: [499] 12030 the connection with the server was terminated abnormally And 10054 Connection reset by peer, what does this mean?

Errors of this kind in the MoonBot terminal log mean that these are bugs appearing on the Binance exchange. To eliminate this kind of errors, we recommend to move MoonBot terminals to the location of Korea (Seoul), since experience has shown that such errors occur only in the location of Japan (Tokyo).

In the log I saw entries like: [499] 12030 the connection with the server was terminated abnormally And 10054 Connection reset by peer, what does this mean? Read More »

In the log I saw something like: UDP Init failed: Could not bind socket. Address and port are already in use. network functions won’t work, sorry, what does it mean?

UDP Init failed: Could not bind socket. Address and port are already in use. Network functions won’t work, sorry” in the MoonBot terminal log occurs when you run multiple copies of the MoonBot terminal with the same port number.To make this disappear, in each MoonBot terminal, add its unique port in the “Listen UPD port:”

In the log I saw something like: UDP Init failed: Could not bind socket. Address and port are already in use. network functions won’t work, sorry, what does it mean? Read More »

I’ve seen entries in the log like: Order does not exist, what does it mean?

This type of error in the MoonBot terminal’s log means that an old Binance bug has appeared, but it’s still relevant. It means that API GET /api/v3/order function to check order status returns error “Order does not exist”, although the order actually exists. Due to this error, it is impossible to check the order status

I’ve seen entries in the log like: Order does not exist, what does it mean? Read More »