Log errors

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.

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

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

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.

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)

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

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).

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:”

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

Error [499] Err: Read timed out and other errors with the code [499] usually mean a problem with the connection on your side (ISP, Internet, router). Less often – a global network failure on the exchange side.