Masternode troubleshooter

The Helium wallet allows you to run the essential Masternode commands from the GUI on the Masternodes tab. However, if things aren't working as they should, the easiest way to diagnose the problems is through the command line. You can follow the below steps to see if everything is set up and working correctly.

Note that it can currently take up to a day for your masternode to start earning rewards. As the network grows so will the waiting time. If the first two commands below return the desired result: just wait a bit more. Before you make changes in the .conf files of your VPS, always stop the client first. After you make changes in your local .conf files, always restart your wallet afterwards.

If you installed using Nodemaster: the commands there are slightly different. Preclude every command with sudo /usr/local/bin/helium-cli -conf=/etc/masternodes/helium_n1.confwhere n1 is the nr. of your masternode. So helium-cli masternode status becomes sudo /usr/local/bin/helium-cli -conf=/etc/masternodes/helium_n1.conf masternode status etcetera.

* On your controller wallet, enter masternode list-conf in the debug console. Make sure the status of your masternode is enabled/active. Sample output:

"alias": "nodealias1",

• On your Masternode wallet (your VPS), enter helium-cli masternode status and check that it returns Masternode succesfully started. Also make sure the addr entry matches the receiving address that holds your 1000 HLM collateral. Sample output:

  "txhash":
  
  

If the above commands returned the desired result: great. All is working as should be and all you have to do is wait. If not, continue below.

• Still on your Masternode wallet enter helium-cli getblockcount and make sure it matches the block count of your wallet and that of the blockexplorer. If it doesn't. Stop your masternode with helium-cli stop and restart and resync it with sudo heliumd -daemon -resync.
  
  

• On your controller wallet, open the masternode.conf file. Make sure the txhash matches the one in the helium-cli masternode status output of your Masternode wallet. Also check that the IP address matches the address of your VPS. The txhash is the brown entry in this masternode.conf example:

MN1

• On your Masternode wallet, open the helium.conf file with sudo nano ~/.helium/helium.conf and check that the masternodeprivkey entry matches the one in the masternode.conf file of your controller wallet. This is the green entry in the above example. The masternodeprivkey is the key you generated in the controller wallet with the masternode genkey command.
  
  

• Check the masternode list output of both your controller and Masternode wallets (your masternode should on the bottom of the list somewhere). See that the txhashes of both match.
  
  

Notes

The above troubleshooter assumes you either installed Helium from source or copied the files to /usr/local/bin/ on your VPS. If you didn't, you will have to find the folder where the files are (usually in ~/helium-0.16.0/bin/) and issue every command with ./. So helium-cli masternode status becomes ./helium-cli masternode status.