General errors
In order to enter new API keys, you first need to click on "Register another keys", then enter the new API keys in the appropriate fields and then click on "Register API keys".
If the MoonBot terminal does not connect to the exchange and you see in the Settings - Login tab the inscription "Enter the correct API keys" in the upper left corner, then this error may be due to several reasons:
1) You are incorrectly entering API keys in the corresponding fields API key and API secret on the Settings - Login tab.
a) You are trying to enter API key data into the API secret field and vice versa. These data should be entered strictly in their own fields.
b) When you try to copy API keys into the buffer only a part of them is copied, or you have caught an extra space in the buffer.
2) You are entering expired API keys, which exchanger might delete from your account.
3) Your account at the exchange got banned or API keys are present, but there are no ticks permitting trading on the spot or futures market. In addition, we recommend immediately check the presence of API keys in the white IP address from which the MoonBot terminal is allowed to trade.
4) You may have an antivirus installed on your computer, which blocks the connection of the MoonBot terminal to the Internet, in which case the MoonBot can not connect to the exchange.
5) You should also check the Internet connection, restart the router.
6) You should also check the setting of VPN and PROXY services, if you have them connected, perhaps they are blocking the connection between your computer and exchanger addresses.
There are other reasons for this kind of error, for further advice, contact the Moon Bot Public Telegram group: https://t.me/Moon_Bot_Public
1) You are incorrectly entering API keys in the corresponding fields API key and API secret on the Settings - Login tab.
a) You are trying to enter API key data into the API secret field and vice versa. These data should be entered strictly in their own fields.
b) When you try to copy API keys into the buffer only a part of them is copied, or you have caught an extra space in the buffer.
2) You are entering expired API keys, which exchanger might delete from your account.
3) Your account at the exchange got banned or API keys are present, but there are no ticks permitting trading on the spot or futures market. In addition, we recommend immediately check the presence of API keys in the white IP address from which the MoonBot terminal is allowed to trade.
4) You may have an antivirus installed on your computer, which blocks the connection of the MoonBot terminal to the Internet, in which case the MoonBot can not connect to the exchange.
5) You should also check the Internet connection, restart the router.
6) You should also check the setting of VPN and PROXY services, if you have them connected, perhaps they are blocking the connection between your computer and exchanger addresses.
There are other reasons for this kind of error, for further advice, contact the Moon Bot Public Telegram group: https://t.me/Moon_Bot_Public
If you periodically have the Start button pressed and the MoonBot terminal stops working, the reasons for the stops should be looked for in the log and then in the "Settings - Autostart" tab, where you need to check the checkboxes on the following items:
1) In the parameters "Stop If loss greater then": you should disable the checkboxes or increase the threshold values for the bot stop.
2) In "Auto Stop if errors level > = 3" (adjustable by slider): disable checkboxes or increase the values of error threshold.
3) In "Auto Stop if Ping > 1000 ms" (controlled by slider): disable checkmark or increase ping value.
Please note that these settings are protective in the MoonBot terminal and allow you to protect your trading in case of exceeding the loss value, or if there are errors in the API connection with the exchange, or a bad ping, which may lead to freezing of orders and loss of trading positions. Study these options carefully and use these settings knowledgeably as needed!
1) In the parameters "Stop If loss greater then": you should disable the checkboxes or increase the threshold values for the bot stop.
2) In "Auto Stop if errors level > = 3" (adjustable by slider): disable checkboxes or increase the values of error threshold.
3) In "Auto Stop if Ping > 1000 ms" (controlled by slider): disable checkmark or increase ping value.
Please note that these settings are protective in the MoonBot terminal and allow you to protect your trading in case of exceeding the loss value, or if there are errors in the API connection with the exchange, or a bad ping, which may lead to freezing of orders and loss of trading positions. Study these options carefully and use these settings knowledgeably as needed!
For stable MoonBot operation, the clock accuracy must be within plus or minus 50 ms. If the value is much higher, or if the "Clock Accuracy is BAD" message is lit in red, it will cause artifacts on the chart (layering and overlapping of trades). To fix this situation, restart MoonBot as an administrator to give it a higher priority. If this does not help, you need to synchronize the clock in Windows, because your computer time may be behind the current real time.
Using WIN10 as an example, go to Start-Search-Time-Additional date and time settings, Regional settings-Date and time-Internet time-Change settings-Synchronize over Internet. The PC will then synchronize the time with the Windows server.
Periodically you will have to repeat this procedure, if the accuracy of the clock has increased significantly. In addition, it is recommended to install a time synchronization utility, such as NetTime.
If the above tips do not help, contact the Moon Bot Public Telegram group for help: https://t.me/Moon_Bot_Public
Using WIN10 as an example, go to Start-Search-Time-Additional date and time settings, Regional settings-Date and time-Internet time-Change settings-Synchronize over Internet. The PC will then synchronize the time with the Windows server.
Periodically you will have to repeat this procedure, if the accuracy of the clock has increased significantly. In addition, it is recommended to install a time synchronization utility, such as NetTime.
If the above tips do not help, contact the Moon Bot Public Telegram group for help: https://t.me/Moon_Bot_Public
Sometimes the API load indicator becomes red - it signals that the API is experiencing an excessive load at the moment, which can lead to a temporary ban from the exchange. In this case, it is necessary to close unnecessary charts or enable auto-closing charts. If the increased load appears after launching the MoonShot strategy, then reduce the number of orders. Disable auto-open charts at signals from strategies. When trading manually, do not rearrange charts with a large number of orders at the same time. If you plan to run several MoonBot terminals on one bot, start the next one only after the previous one is fully loaded, i.e., not all at once, but sequentially.
MoonBot receives all trades in real time via the websocket protocol. Their absence on the chart indicates that MoonBot does not receive them. If the chart is missing crosses (trades), it may mean that the MoonBot terminal lost connection with the exchange due to Internet problems, lagging exchange, problems with antivirus or firewall on your computer, perhaps the API keys have expired or blocked your account at the exchange. In addition, perhaps the button "Show market history" (second from the right after the Auto Zoom) in the main window of the bot is depressed.
If the above tips do not help, contact the Moon Bot Public telegram group for help: https://t.me/Moon_Bot_Public
If the above tips do not help, contact the Moon Bot Public telegram group for help: https://t.me/Moon_Bot_Public
The problem lies in the Windows system prohibiting you from writing files in the folder where MoonBot is installed, because the guidelines for its placement on the computer are violated.
a) Do not run the MoonBot terminal from the archive;
b) do not unpack MoonBot to the desktop, temporary or system folders in your operating system, such as windows, temp, users, and so on;
c) do not use Cyrillic letters in the folder names in the path to the MoonBot terminal;
d) if your computer has other disks besides the system disk C, for example, such as D, E, etc., then place the folder with the MoonBot terminal on them. If your computer has only the system drive C, then place the folder with the MoonBot on this drive in a separate folder in the root directory, for example, C:\MoonBot.
a) Do not run the MoonBot terminal from the archive;
b) do not unpack MoonBot to the desktop, temporary or system folders in your operating system, such as windows, temp, users, and so on;
c) do not use Cyrillic letters in the folder names in the path to the MoonBot terminal;
d) if your computer has other disks besides the system disk C, for example, such as D, E, etc., then place the folder with the MoonBot terminal on them. If your computer has only the system drive C, then place the folder with the MoonBot on this drive in a separate folder in the root directory, for example, C:\MoonBot.
1) Perhaps some bot menu is open and it is behind the main bot window or out of the monitor area. In this case, you need to press the combination Ctrl+Shift+F10, which moves the active window on top of all the windows in the main monitor area, then close this window and the bot will respond to the controls again.
2) If the MoonBot itself is hung up, you can remove the task in Device Manager.
3) If not only the MoonBot is hung up, but also other applications on your computer, restart the hung up computer.
2) If the MoonBot itself is hung up, you can remove the task in Device Manager.
3) If not only the MoonBot is hung up, but also other applications on your computer, restart the hung up computer.
First, you should check all of these options:
1) The trade-enabling checkboxes in the API keys on the exchange are not checked.
2) The Start button on the main window of the MoonBot terminal is not pressed.
3) There is no or insufficient trading balance (balance is indicated in the top left corner of the main window of the MoonBot terminal).
4) An order is set less than the minimum allowable lot on a coin.
5) If you have FREE version, it is possible to expose orders only on BTC pairs and if you have switched to pair USDT, orders will not be exposed on FREE.
6) Attempt to expose the order with wrong combinations of keys and mouse clicks.
7) The order is placed not on the glass, but on the chart.
8) The strategy does not pass through the filters. Enable the "Filters on charts" (Funnel) button and see which filters do not allow the strategy to work and put the order on the chart. If necessary, adjust the parameters of the filters or temporarily disable them by setting Ignore Filters = YES.
9) The manual strategy is not set up correctly.
10) The exchange might give a ban, in this case, it is worth to wait for some time. First ban is written for 5 minutes, if spam from IP to exchanger continues from bot, exchanger writes ban for a longer time.
Other causes are possible, more accurately determine the cause of error with help of logs. If you cannot cope with this problem, for more detailed advice, contact the Moon Bot Public Telegram group: https://t.me/Moon_Bot_Public
1) The trade-enabling checkboxes in the API keys on the exchange are not checked.
2) The Start button on the main window of the MoonBot terminal is not pressed.
3) There is no or insufficient trading balance (balance is indicated in the top left corner of the main window of the MoonBot terminal).
4) An order is set less than the minimum allowable lot on a coin.
5) If you have FREE version, it is possible to expose orders only on BTC pairs and if you have switched to pair USDT, orders will not be exposed on FREE.
6) Attempt to expose the order with wrong combinations of keys and mouse clicks.
7) The order is placed not on the glass, but on the chart.
8) The strategy does not pass through the filters. Enable the "Filters on charts" (Funnel) button and see which filters do not allow the strategy to work and put the order on the chart. If necessary, adjust the parameters of the filters or temporarily disable them by setting Ignore Filters = YES.
9) The manual strategy is not set up correctly.
10) The exchange might give a ban, in this case, it is worth to wait for some time. First ban is written for 5 minutes, if spam from IP to exchanger continues from bot, exchanger writes ban for a longer time.
Other causes are possible, more accurately determine the cause of error with help of logs. If you cannot cope with this problem, for more detailed advice, contact the Moon Bot Public Telegram group: https://t.me/Moon_Bot_Public
The main reason why the strategy does not place a Buy order in the MoonBot terminal may be several:
1) The trade-enabling checkboxes are not set in the API keys on the exchange.
2) The Start button on the main window of the MoonBot terminal is not pressed.
3) There is no or insufficient trading balance (balance is indicated in the top left corner of the main window of the MoonBot terminal).
4) The order is set less than the minimum allowable lot on the coin in the main settings or in the strategy settings in the OrderSize parameter.
5) If you have FREE version, it is possible to expose orders only on BTC pairs and if you have switched to pair USDT, orders will not be exposed on FREE.
6) Make sure that on the main window the button "Mode:" is set in position "Mode: Signals" and is green.
7) Check that the "Autodetect:" button on the main window is set to "Autodetect: ON".
8) The strategies are not activated (to activate them, you must check the box for the desired strategies and click on the button "Start Checked"). The light on the left side of the activated strategies will be on.
9) The strategy on the Buy conditions tab is not checked for auto-buy. AutoBuy is working, if the parameter is set like this: AutoBuy=YES.
10) The strategy does not pass through the filters. Activate the "Chart Filters" (Funnel) button and check which filters prevent the strategy from triggering and placing an order on the chart. If necessary, adjust the filter parameters or temporarily disable them by setting Ignore Filters = YES.
11) The strategy does not pass the conditions of the parameters on the Settings-Main tab in the "Good pump" conditions" and "Risk limit conditions" zones, to exclude this reason, uncheck all the parameters in these settings.
12) The exchange could give out a ban, in this case it is necessary to wait some time. The first ban is written for 5 minutes, if spam from IP to exchanger continues from bot, exchanger writes ban for a longer time.
Other causes are possible, more accurately determine the cause of error with help of logs. If you cannot cope with this problem, for more detailed advice, contact the Moon Bot Public Telegram group: https://t.me/Moon_Bot_Public
1) The trade-enabling checkboxes are not set in the API keys on the exchange.
2) The Start button on the main window of the MoonBot terminal is not pressed.
3) There is no or insufficient trading balance (balance is indicated in the top left corner of the main window of the MoonBot terminal).
4) The order is set less than the minimum allowable lot on the coin in the main settings or in the strategy settings in the OrderSize parameter.
5) If you have FREE version, it is possible to expose orders only on BTC pairs and if you have switched to pair USDT, orders will not be exposed on FREE.
6) Make sure that on the main window the button "Mode:" is set in position "Mode: Signals" and is green.
7) Check that the "Autodetect:" button on the main window is set to "Autodetect: ON".
8) The strategies are not activated (to activate them, you must check the box for the desired strategies and click on the button "Start Checked"). The light on the left side of the activated strategies will be on.
9) The strategy on the Buy conditions tab is not checked for auto-buy. AutoBuy is working, if the parameter is set like this: AutoBuy=YES.
10) The strategy does not pass through the filters. Activate the "Chart Filters" (Funnel) button and check which filters prevent the strategy from triggering and placing an order on the chart. If necessary, adjust the filter parameters or temporarily disable them by setting Ignore Filters = YES.
11) The strategy does not pass the conditions of the parameters on the Settings-Main tab in the "Good pump" conditions" and "Risk limit conditions" zones, to exclude this reason, uncheck all the parameters in these settings.
12) The exchange could give out a ban, in this case it is necessary to wait some time. The first ban is written for 5 minutes, if spam from IP to exchanger continues from bot, exchanger writes ban for a longer time.
Other causes are possible, more accurately determine the cause of error with help of logs. If you cannot cope with this problem, for more detailed advice, contact the Moon Bot Public Telegram group: https://t.me/Moon_Bot_Public
Such problems may occur if there are general problems with your computer, then you need to restart your computer, run MoonBot in administrator mode, and try copying strategies again. It can also be due to a Windows clipboard problem, where capitalized words are not copied to the clipboard. If there are coins in the strategy's whitelist or blacklist, you should rewrite them in lowercase letters, for example correct from BTC to btc and try again. Also try copying strategies with CTRL+C (copy to clipboard) and paste with CTRL+V (paste from clipboard).
For this purpose, the MoonBot terminal has a hanged position tracking feature that is available only in the PRO version.
The Control hanged position function is enabled in Settings-Advanced-Hang Control and can be configured as follows:
1) The Control orders of this bot should be ticked on the working bot, optionally for ping control in the Control VDS IP field, set the IP of the VDS with the tracking bot.
2) Setting up tracking bots:
You need to open the UDP port specified in the bot in the line "Open UDP port 2704 in the VDS with control bot". Warning! Spot and different futures pairs use different ports. These ports are used for ping control.
Then you need to fill in the table of API keys from the worker bots. API keys must be from different exchange accounts! If you enter API keys from the same account in two lines, the bot will not be able to correctly determine which account should be managed and will mark both lines with API keys in the Status column as duplicate.
If API keys are entered incorrectly, or no rights are set for them, or IP whitelist, the "Status" column will show an error.
The "O" checkbox in the table is responsible for controlling orders by time of existence (Time, s column) and by distance to the current price (Price, % column). The order will be cancelled after reaching the specified time or approaching the specified price distance.
The "P" checkbox is responsible for position control. If it is enabled, the bot will detect positions hanging without take-outs and report about them in Telegram, and with AutoSell ticked, it will also automatically sell. In the "Dont control these balances" field you can set the Black List of coins excluded from the position control algorithm. The default coins are: BTC, ETH, BNB, USDP, TUSD, TUSD, USDC, USDT, BUSD, GBP, USD, RUB, EUR, HT, HUSD, TRY.
Auto-selling is performed by a special manual strategy called "SafeGuard" - this strategy is created automatically at the first such sale, after which you can edit its settings.
The IP tick is responsible for ping control. If the IP of the tracking bot is correctly set in the working bot, and if the ping does not pass within 10 seconds, then orders to open positions will be cancelled (this does not apply to take trades, the algorithm of controlling hung positions does not cancel take trades).
3) Number of tracking bots:
For spot: 1 bot monitors all accounts (and will cancel orders for all pairs; look for and sell hover positions for the base currency it works on).
For futures: 1 bot for each market (it will cancel orders and search for hovering positions only for the market on which it works).
Total number of tracking bots required is as follows:
1 bot tracking the spot market of Binance exchange
1 bot tracking the USDT futures market on Binance exchange
1 bot tracking the Binance quarter market
1 bot tracking the spot market on Huobi exchange
1 bot tracking the spot market on Bybit exchange
1 bot tracking the futures market on Bybit exchange
1 bot tracking the spot market on Gate exchange
1 bot tracking the futures market on Gate exchange
20-30 API keys can be inserted into each tracking bot. A larger number of entered keys can lead to an API ban at the moment when the bot starts cancelling all orders on all accounts at once; therefore, if there are more than 30 accounts, it is required to additionally separate the tracking bots on different servers, as the API load is counted by server IP and so that each bot has no more than 30 API keys.
2) Setting up tracking bots:
You need to open the UDP port specified in the bot in the line "Open UDP port 2704 in the VDS with control bot". Warning! Spot and different futures pairs use different ports. These ports are used for ping control.
Then you need to fill in the table of API keys from the worker bots. API keys must be from different exchange accounts! If you enter API keys from the same account in two lines, the bot will not be able to correctly determine which account should be managed and will mark both lines with API keys in the Status column as duplicate.
If API keys are entered incorrectly, or no rights are set for them, or IP whitelist, the "Status" column will show an error.
The "O" checkbox in the table is responsible for controlling orders by time of existence (Time, s column) and by distance to the current price (Price, % column). The order will be cancelled after reaching the specified time or approaching the specified price distance.
The "P" checkbox is responsible for position control. If it is enabled, the bot will detect positions hanging without take-outs and report about them in Telegram, and with AutoSell ticked, it will also automatically sell. In the "Dont control these balances" field you can set the Black List of coins excluded from the position control algorithm. The default coins are: BTC, ETH, BNB, USDP, TUSD, TUSD, USDC, USDT, BUSD, GBP, USD, RUB, EUR, HT, HUSD, TRY.
Auto-selling is performed by a special manual strategy called "SafeGuard" - this strategy is created automatically at the first such sale, after which you can edit its settings.
The IP tick is responsible for ping control. If the IP of the tracking bot is correctly set in the working bot, and if the ping does not pass within 10 seconds, then orders to open positions will be cancelled (this does not apply to take trades, the algorithm of controlling hung positions does not cancel take trades).
3) Number of tracking bots:
For spot: 1 bot monitors all accounts (and will cancel orders for all pairs; look for and sell hover positions for the base currency it works on).
For futures: 1 bot for each market (it will cancel orders and search for hovering positions only for the market on which it works).
Total number of tracking bots required is as follows:
1 bot tracking the spot market of Binance exchange
1 bot tracking the USDT futures market on Binance exchange
1 bot tracking the Binance quarter market
1 bot tracking the spot market on Huobi exchange
1 bot tracking the spot market on Bybit exchange
1 bot tracking the futures market on Bybit exchange
1 bot tracking the spot market on Gate exchange
1 bot tracking the futures market on Gate exchange
20-30 API keys can be inserted into each tracking bot. A larger number of entered keys can lead to an API ban at the moment when the bot starts cancelling all orders on all accounts at once; therefore, if there are more than 30 accounts, it is required to additionally separate the tracking bots on different servers, as the API load is counted by server IP and so that each bot has no more than 30 API keys.
The reasons why the inadequately low sale/purchase price is not a bug, but a feature of the average sale price display.
The main reason why the sale visually occurs, for example, at an inadequately low price: the number of coins bought is greater than the number of coins sold.
Example: bought 100 coins for $100, sold 90 coins for $90
The average purchase price = 100 / 100 = $1. Average selling price = 90 / 100 = $0.9
Why do we divide by 100 coins, even though only 90 coins were sold? Because the rest of 10 coins is impossible to sell (limit of exchanges for minimal order). You had 100 coins, as a result of their sale you have 90$, so the bot counts the average price as a result of selling 100 coins for 90$.
Why does the balance of coins appear? There could be several reasons:
1) You are trading without a balance of BNB coins. In this case, the exchange deducts the commission in the traded coins and the multiplicity of the lot is violated. For example, there were 2 coins, 0.1 was written off, the remaining 1.9 coins. And you can only sell multiples of 1 coin, so 0.9 will hang in the exchange as a residue.
2) You have BNB, but other traders trade without BNB. For example, you sell a 2 coin order into the wall with 1.9. Then you try to re-move the order, it is canceled, but it cannot be placed anymore as it is less than the minimum lot and 0.1 coin remains on the balance.
a) If you cancel a partially executed order, the unsold coins will remain on your balance. If "Cancel small SELLs" is checked, the MoonBot will delete such orders where the balance is less than a lot. The order will only be removed from the list of active from the chart, but it will remain in the report and in the exchange. The meaning of this checkbox - to remove from the screen orders, which you still can not manage, due to the fact that they are less than a lot, hence they can not be moved.
b) Another variation of the case of item 2: You move an order to sell, at which point it is partially filled, and the remainder is already less than a lot, and it cannot be moved. In the log there will be a record "Looks like order was done while replacing or rest quantity too low".
3) During listing, the commission for the first hours is written off in coins, not BNB, which always results in balances.
How do you check that you have balances?
1) You can open a spot wallet overview and there you will see your coin balances.
2) You can open the history of orders, find the desired order, expand the history of trades and check if the commission was charged in BNB or coins, and also check how much was bought and how much was sold.
All of the above can fully apply to the incorrect purchase price.
Briefly summarizing:
1) Always maintain a balance of BNB coins for trade commission deductions.
2) Regularly check the small balances of coins in your exchange account balance and convert them to BNB in time.
The main reason why the sale visually occurs, for example, at an inadequately low price: the number of coins bought is greater than the number of coins sold.
Example: bought 100 coins for $100, sold 90 coins for $90
The average purchase price = 100 / 100 = $1. Average selling price = 90 / 100 = $0.9
Why do we divide by 100 coins, even though only 90 coins were sold? Because the rest of 10 coins is impossible to sell (limit of exchanges for minimal order). You had 100 coins, as a result of their sale you have 90$, so the bot counts the average price as a result of selling 100 coins for 90$.
Why does the balance of coins appear? There could be several reasons:
1) You are trading without a balance of BNB coins. In this case, the exchange deducts the commission in the traded coins and the multiplicity of the lot is violated. For example, there were 2 coins, 0.1 was written off, the remaining 1.9 coins. And you can only sell multiples of 1 coin, so 0.9 will hang in the exchange as a residue.
2) You have BNB, but other traders trade without BNB. For example, you sell a 2 coin order into the wall with 1.9. Then you try to re-move the order, it is canceled, but it cannot be placed anymore as it is less than the minimum lot and 0.1 coin remains on the balance.
a) If you cancel a partially executed order, the unsold coins will remain on your balance. If "Cancel small SELLs" is checked, the MoonBot will delete such orders where the balance is less than a lot. The order will only be removed from the list of active from the chart, but it will remain in the report and in the exchange. The meaning of this checkbox - to remove from the screen orders, which you still can not manage, due to the fact that they are less than a lot, hence they can not be moved.
b) Another variation of the case of item 2: You move an order to sell, at which point it is partially filled, and the remainder is already less than a lot, and it cannot be moved. In the log there will be a record "Looks like order was done while replacing or rest quantity too low".
3) During listing, the commission for the first hours is written off in coins, not BNB, which always results in balances.
How do you check that you have balances?
1) You can open a spot wallet overview and there you will see your coin balances.
2) You can open the history of orders, find the desired order, expand the history of trades and check if the commission was charged in BNB or coins, and also check how much was bought and how much was sold.
All of the above can fully apply to the incorrect purchase price.
Briefly summarizing:
1) Always maintain a balance of BNB coins for trade commission deductions.
2) Regularly check the small balances of coins in your exchange account balance and convert them to BNB in time.
"Binance Exchange according to the new security rules, which were announced in advance, began to remove API keys that do not have in the white list of allowed IP addresses.
Due to this, MoonBot terminals using these keys stop on errors and cannot connect on reboot.
To solve this problem and restore the PRO version (if available), you need to do the following:
Strictly follow point by point!
1) Close MoonBot and back it up (to restore and retry).
2) Go to your account at Binance exchange and create NEW API keys (it's very important that the keys were new and not previously registered in the bot), at the same time you need to choose the type of keys Generated by the system.
3) New keys have only read permission, so further you will need to edit restrictions and specify in the white list allowed IP addresses from which these keys will work, if this is not done, the security system will not allow you to check the right checkboxes.
For those who have a dynamic IP address and it is periodically changed by the provider, you will need to either get a static address, or use a VPN or VDS (dedicated server). Otherwise, Binance will remove the API keys again.
4) After specifying the IP address in the white list, check the permissions for spot and futures trading, not forgetting to save the public and secret part of the key in a text form in a separate file (this file must be kept on a separate flash drive).
5) Run the MoonBot terminal, which previously worked for you on the remote API keys. Especially important, if you restore the PRO version, you must run the same bot.
6) Open the Settings-Login tab, completely delete the old API keys and insert the NEW ones.
7) Once you have inserted the new keys click Register API Keys.
The terminal will check if the new API keys belong to the same account, which were registered to it earlier. If you've done everything correctly, the MoonBot will connect to your Binance account and reconnect.
Due to this, MoonBot terminals using these keys stop on errors and cannot connect on reboot.
To solve this problem and restore the PRO version (if available), you need to do the following:
Strictly follow point by point!
1) Close MoonBot and back it up (to restore and retry).
2) Go to your account at Binance exchange and create NEW API keys (it's very important that the keys were new and not previously registered in the bot), at the same time you need to choose the type of keys Generated by the system.
3) New keys have only read permission, so further you will need to edit restrictions and specify in the white list allowed IP addresses from which these keys will work, if this is not done, the security system will not allow you to check the right checkboxes.
For those who have a dynamic IP address and it is periodically changed by the provider, you will need to either get a static address, or use a VPN or VDS (dedicated server). Otherwise, Binance will remove the API keys again.
4) After specifying the IP address in the white list, check the permissions for spot and futures trading, not forgetting to save the public and secret part of the key in a text form in a separate file (this file must be kept on a separate flash drive).
5) Run the MoonBot terminal, which previously worked for you on the remote API keys. Especially important, if you restore the PRO version, you must run the same bot.
6) Open the Settings-Login tab, completely delete the old API keys and insert the NEW ones.
7) Once you have inserted the new keys click Register API Keys.
The terminal will check if the new API keys belong to the same account, which were registered to it earlier. If you've done everything correctly, the MoonBot will connect to your Binance account and reconnect.
In the left corner is the status of the connection of the bot with the exchange, possible options: the green inscription "Ready" means that the bot has successfully connected to the exchange and receives from it via API all the necessary data for the bot or the red inscription "Connection ERROR", which would mean that the bot has problems connecting to the exchange, which may be associated with incorrect API key entry or lack of permissions to trade, internet problems, anti-virus blocking or other computer glitches. If you can't find the cause of such an error on your own, then please contact the Moon Bot Public Telegram group: https://t.me/Moon_Bot_Public
Circle or "traffic light", its color indicates the quality of the connection to the exchange, if the light is green, then everything is fine, if the light is orange, then there are problems with the connection or a significant slowdown. In this case, you can try to change the methods of connecting to the exchanger, restart the router or wait for the lags in the exchanger to stop.
Most likely, you have one of the windows with Settings, Reports, MarketsTable and Strategies open and this window is behind the main window of the MoonBot terminal or outside the working area of the monitor. In order to return the strategies window to the main window of the MoonBot terminal and in the visible area of the monitor, you should press the combination of hot keys, which can be set in the Settings - Hotkeys tab in the "Reset form positions" field; by default, the combination is: Ctrl+Shift+F10. It's also possible that the MoonBot terminal may hang for various reasons related to the operating system, in this case, you should restart your computer and load the MoonBot terminal again in administrator mode.
If the Settings, Reports, Show Markets and Strategies windows do not open, it is likely that the window you are calling is behind the main window of the MoonBot terminal or outside the working area of the monitor. In order to return the strategies window to the main MoonBot terminal window and in the visible area of the monitor, you should press the hotkeys combination that can be set in the Settings-HotKeys tab in the "Reset form positions" field; by default, the combination is: Ctrl+Shift+F10.
To clear the Hotkeys field, click on the field with your mouse and then press ESC on your keyboard.
In the MoonBot terminal, the mode of hiding balance through Hotkeys is activated, which is set to F7 by default. If after pressing F7 the balance is still fuzzy, you should go to the Settings - Hotkeys tab and check the value of the combination in the "Hide Balance" field and press the button combination specified in this field.
In the MoonBot terminal, the emulator orders, whether they are set when the Emulation mode is enabled through the menu or set when the EmulatorMode=YES parameter is checked in the strategy - DO NOT JOINED or SPLITTED!
These icons on the chart appear automatically and are not specially disabled. Wait a while and they will appear after a while on the spot chart of the MoonBot terminal.
You trade in the MoonBot terminal on the USDT pair and see the arrow from the parallel BTC pair, which appears paler on the chart. To avoid confusion, make these arrows from the parallel pair (BTC) paler in Settings - User Interface - Color Setup or change their color a little to distinguish the chart of the parallel pair.
If it bothers you, you can disable the display of trades in the BTC pair, by right-clicking on the "Show Spot trades\OrderBook" button, which is situated to the left of the "Funnel" button, and uncheck the "Show BTC Trades" option in the menu. But it's better not to do it, because the shoots at the parallel trading pair can be a hint that the buyers and sellers are still fighting and the price at your pair can still grow, at least to the level of the shoot.
If it bothers you, you can disable the display of trades in the BTC pair, by right-clicking on the "Show Spot trades\OrderBook" button, which is situated to the left of the "Funnel" button, and uncheck the "Show BTC Trades" option in the menu. But it's better not to do it, because the shoots at the parallel trading pair can be a hint that the buyers and sellers are still fighting and the price at your pair can still grow, at least to the level of the shoot.
If you in the MoonBot terminal place pending orders (Pending order) in the red or green glass manually or with strategies (BuyStop or BuyLimit pending order type), the pending order has two lines:
- a solid (trigger) line through which the price line must pass (not crosses with trades) and if it triggers, it disappears from the chart.
- a dashed line (the place of placing a Buy order), after the solid line has triggered and disappeared from the chart, a real Buy order is immediately placed in place of the dashed line.
It is possible to adjust the position of the dotted line and set it above or below the solid line in order to buy a coin right after placing a Buy order or to place a Buy order within the spread or below the spread in the trading window at some distance from the market. The dotted line is displayed on the tab "Settings Interface" - tick the box "Draw pending orders buy price".
When manually placing pending orders, the distance from the dotted line to the solid line is set in the "Pending orders spread" field of the Settings - User Interface - you should set the values with the plus or minus sign in those fields, which will affect the distance and position (above or below the solid line) of the dotted line against the solid line.
During automatic placing of the pending orders (BuyStop and BuyLimit) the distance from the dotted line to the solid line is set in the strategy settings on the Buy conditions tab by the value in the PendingOrderSpread parameter, which should be written with a plus or minus sign, according to your algorithm.
So, in your case, the pending order did not trigger, since the price line did not cross it (a solid line of the pending order), and the crossing was only with crosses of trades, which do not trigger the pending order. To be sure of this, disable the crosses on the chart using the Show market history button (on the main window of the MoonBot terminal the second button to the right of the Auto Scale button) and leave only the price line. Exactly it must cross the solid line of the pending order, so that the pending order (solid line) will be triggered, disappear from the chart and put the Buy order in place of the dotted line.
- a solid (trigger) line through which the price line must pass (not crosses with trades) and if it triggers, it disappears from the chart.
- a dashed line (the place of placing a Buy order), after the solid line has triggered and disappeared from the chart, a real Buy order is immediately placed in place of the dashed line.
It is possible to adjust the position of the dotted line and set it above or below the solid line in order to buy a coin right after placing a Buy order or to place a Buy order within the spread or below the spread in the trading window at some distance from the market. The dotted line is displayed on the tab "Settings Interface" - tick the box "Draw pending orders buy price".
When manually placing pending orders, the distance from the dotted line to the solid line is set in the "Pending orders spread" field of the Settings - User Interface - you should set the values with the plus or minus sign in those fields, which will affect the distance and position (above or below the solid line) of the dotted line against the solid line.
During automatic placing of the pending orders (BuyStop and BuyLimit) the distance from the dotted line to the solid line is set in the strategy settings on the Buy conditions tab by the value in the PendingOrderSpread parameter, which should be written with a plus or minus sign, according to your algorithm.
So, in your case, the pending order did not trigger, since the price line did not cross it (a solid line of the pending order), and the crossing was only with crosses of trades, which do not trigger the pending order. To be sure of this, disable the crosses on the chart using the Show market history button (on the main window of the MoonBot terminal the second button to the right of the Auto Scale button) and leave only the price line. Exactly it must cross the solid line of the pending order, so that the pending order (solid line) will be triggered, disappear from the chart and put the Buy order in place of the dotted line.
If the chart has disappeared information about the trading session on the coin, it means that the Multi order mode is off. To activate Multi order mode, you need to press the M button on the main window of the MoonBot and information about the trading session on the coin will appear again.
If your strategy was placing Buy orders in the MoonBot terminal in emulator mode, but does not do so when you switch to real mode, check the size of the Buy order being placed. The parameter OrderSize, which is located on the Buy conditions tab of the strategy settings, is responsible for the size and order of placing Buy orders in the strategy. If OrderSize=0, the size of the Buy order will be taken from the bar or fixed button on the main window of the MoonBot terminal, which are responsible for the size of the Buy order. If the OrderSize parameter is set to a specific order size in BTC, then the MoonBot terminal will place a Buy order for the coin with the specified size. Please note that the Free version has a maximum order limit of $40 (in BTC equivalent), and you cannot place a Buy order below the minimum lot size on a coin (usually $5 in BTC equivalent). Accordingly, the OrderSize in the strategy settings should be between $5 and $40 (in BTC equivalent), but we recommend placing orders between $10 and $35 (in BTC equivalent) to keep within this corridor when the BTC rate changes.
We recommend that you update your MoonBot terminal to the latest version, as the new versions have fixed the error of taking profit on simultaneous buy orders that exceed the position limit.
If you are updating the MoonBot terminal and you get an "Update Fail. Please download latest Moonbot from our site", you should first make sure that the MoonBot terminal is closed. Then download the archive with the latest version of the terminal from our website https://moon-bot.com/en/download/, open it and move 4 files from it to the root folder with the MoonBot terminal and replace the files. After that, run the MoonBot.exe file from the root folder in administrator mode and, after the terminal starts, verify that the upgrade to the new version was successful (the version number is indicated in the upper left corner of the MoonBot main window).
Bybit API does not support conversion of small coin balances yet, so there is a Convert to MNT button in MoonBot terminal for Bybit exchange, but when you press it, conversion is not performed and the log shows Currently Bybit does not support auto-conversion, this functionality will work after the exchange will add the ability to convert in the API. Now the remaining coins must be converted manually in your Bybit account.
You can convert small amounts to MNT tokens on Bybit exchange only once every 6 hours. The value of the asset exchange per transaction cannot exceed 0.001 in VTS equivalent. Withdrawn coins (delisting) cannot be exchanged. Requests for conversion of several assets sent from a single trading account can be executed only partially. For each conversion, the Bybit exchange charges 2% of the amount of converted MNT tokens.