Indexer issue:

• Some validators may experience that a red Indexer label appears next to the name of their node in the validator node selection list in Explorer, and after selecting the validator, they see the text Indexer connecting… and outdated data.
• Putting the validator into chill mode, restarting it (if it is no longer selected in the current validator subset), and then unchilling it typically resolves the issue, but the phenomenon may occur again after that.
• This can mostly occur with users who operate multiple validator machines using the same internet source. We are currently investigating the exact cause of this. It is important to note that the indexer is responsible for properly organizing and displaying blockchain data, but it is not necessary for validation: regardless of this, the validator – if not put into chill mode – can produce blocks and receive rewards.

Authorize Proxy stuck:

• After signing the transaction in SubWallet on the Authorize Proxy screen, you may not be able to proceed because the two-factor authentication pop-up window does not appear. We have already released a fix for this issue.
• We have scheduled the application updates for Mondays and Tuesdays. The updates will reach all machines we see (powered on and with a live internet connection) within 24 hours, so you can expect a fresh version on Wednesdays, so it is worth checking the node operation on Wednesdays and Thursdays.

Technical customer service:

• We process incoming emails continuously, in the order they are received. With our current email traffic, this may take several days.
• Please note that Mosaic Chain’s technical customer service can only provide assistance with technical issues related to the Mosaic blockchain and the applications they write (e.g. Validator OS, VPN Controller, Explorer, etc.).
• As a developer, we cannot provide information on business-related issues (commissions, web office, package purchases, email address and password changes), as well as issues related to your Internet connection and its operation (which may differ from validator to validator and we have no insight or influence on them at all).
• Please note that we do not investigate unsupported operational errors! For example, if you run multiple validator nodes on one machine and one validator consumes the resource before the other, or if you run a non-physical machine (you use a cloud service), or if you use virtual machines as validators. In such cases, you will need to fix the operational problems yourself. (With the appropriate expertise, these are of course possible, but we devote our own resources to supporting those who have adhered to the one machine, one validator rule.)
• Devnet and Mainnet run in parallel. Please help our work by indicating in the subject of your letter whether it applies to Devnet or Mainnet!
• In the subject line of every email sent to this address, indicate as the first word that your message concerns Mainnet or Devnet (e.g. Mainnet – sampling problem or Devnet – indexer not synchronizing)
• We will process it in this order: Mainnet, Devnet, all subsequent emails
• So, if you did not start the subject line with Mainnet or Devnet, your email will automatically be moved to the very end of the processing queue.
• When reporting a bug, make sure that in addition to a precise description of the problem, you also attach a photo of the phenomenon, otherwise, despite our best efforts, we will not be able to process your request! We also ask that you copy your wallet address and the name of your validator into the text of the message! If you would like to send another email on the same topic in the future, please do so as a reply to our reply to your previous email regarding this issue!
• You will receive an automatic reply to your email to our technical support – info@mosaicchain.io -, which always includes our suggested solutions for the errors you are experiencing. If the subject of your email is related to one of these, you will only receive our automatic reply and we will not send you any further emails.

DEVNET information:

We hope that you have gained sufficient proficiency on the Devnet for practice and testing purposes before using the Mainnet! On the Mainnet – due to the characteristics of blockchain technology – we usually no longer have the opportunity to find and correct user errors, and lack of practice can result in irreversible – even serious financial – errors on your part!

The latest Devnet version number is “1.0.2“, which you can check by entering the – cat /opt/mosaic/mosaic-stack.version – command on the Valdiator machine.

The latest Mainnet version number is “1.0.2“, which you can check by typing – cat /opt/mosaic/mosaic-stack.version – on the validator machine.

The Mainnet contains all patches released for Devnet. So the Mainnet works the same as the Devnet. 

For those who didn’t have a problem on Devnet, it shouldn’t be on Mainnet either.

In case of a problem on Devnet, first check if you are using the latest version of the OS! When you experience internet overuse/overload, it is extremely important to check the version number of the Mosaic Stack based on the instructions below, and then be sure to include this information in your email!

Checking the Devnet version on your computer:

1. Click on the button labeled Validator Dashboard in the top right of Explorer!
2. Select the name of your node, enter your username and password, and then press the login button!
3. Check if you see the version number indicated as the latest in this email above the Mosaic Stack version number in the rectangle labeled “Installed Packages”!

• If you see the version number indicated above, then you have received the update, check if your node is working correctly!
• Let us know if your problem is solved! (We would also like to hear from you if you have experienced correct operation)
• If you do not see the above version numbers on the Validator Dashboard, the update was not automatically installed on your machine. In this case, you can install the update manually as described below.

Manually install the update: (Do this only if you do not see the version number indicated above!)

Only one of the 3 options below needs to be completed. Start with option I! If the update failed, proceed to the next option!

Option I (update via the Validator Dashboard):

1. Go to the Validator Dashboard (https://devnet-explorer.mosaicchain.io/sign-in)!
2. Select the name of the validator you want to update, enter your username and password, and then click the Continue button to log in!
3. In the upper right corner of the “Installed Packages” rectangle, click the update button with arrows, this will also allow you to manually update the Mosaic Stack.
4. Wait 5-10 minutes, then reload the page and check if the Mosaic Stack version number indicated as the latest in our letter appears.

• If so, the update was successfully installed. Make sure that your machine is in the “Active” state (if not, click the Unchill button), and then check if you experience any malfunctions!
• When you do not see the version number indicated as the latest above, proceed to option II!

Option II (update directly on the validator machine, by issuing a command):

1. Connect a monitor and a keyboard to the validator machine!
2. Turn on the machine, if it is not on!
3. Log in to the validator machine:

• When the login text appears on the screen, enter your username that you entered when installing the machine, then press the Enter key!
• After that, the Password text appears, in which case you must enter your password. For security reasons, the characters do not appear on the screen when you enter the password, but the keystrokes are detected regardless. All you have to do is enter it “blindly” when the system asks for the password, then press the Enter key, and if the password is correct, it will allow you to continue.

4. After successful login, enter the following command exactly as it is written below. It cannot start with a space and cannot end with a space, but you must type a space after the word “sudo”. Once you have entered the command, you can indicate to the computer that you are finished entering it by pressing the Enter key and it can execute the command. The command to enter is: sudo /opt/mosaic/update-mosaic.sh
5. Wait 5-10 minutes, after which the node will automatically appear on the Devnet Explorer interface (https://devnet-explorer.mosaicchain.io/).
6. Go to the Validator Dashboard, log in, and then check in the “Installed Packages” box to see if you see the latest Mosaic Stack version number.

• If so, the update was successfully installed. Make sure your machine is in the “Active” state (if not, click the Unchill button), and then check if you experience any malfunctions!
• When you do not see the latest version number, proceed to option III!

Option III. (updating directly on the validator machine, issuing a command, temporarily stopping the chain service):

1. If you are not logged in on the validator machine, log in!
2. After successfully logging in, type the following command exactly as it is written below. It cannot start with a space and cannot end with a space, but you must type a space after the word “sudo”. Once you have typed the command, you can press Enter to tell the computer that you are done typing and that it can execute the command. The commands to type are as follows (press Enter at the end of each line):sudo systemctl stop mosaic-chain-devnet.servicesudo /opt/mosaic/update-mosaic.shsudo systemctl start mosaic-chain-devnet.service
3. Wait 5-10 minutes, after which the node will automatically appear in the Devnet Explorer interface (https://devnet-explorer.mosaicchain.io/).
4. Go to the Validator Dashboard, log in, and check the “Installed Packages” box to see if you see the latest Mosaic Stack version.

• If so, the update was successfully installed. Make sure your machine is in the “Active” state (if not, click the Unchill button), and then check if you experience any malfunctions!
• If you don’t see the latest version, let us know and we’ll help you move forward!