Quote from: Grandpa Jones on March 20, 2016, 09:32:37 PM

Quote from: Grandpa Jones on March 20, 2016, 07:18:37 AM

I get a similar problem with 1.0.2.0 but not 1.0.1.0

When enabling from the controller with start-alias, everything looks fine, with a "result":"successful".

Checking the debug.log of the masternode I can see the correct "Got NEW Masternode entry -" line (identified by txid). Then with masternode list, I can see the correct line "ENABLED" (identified by txid).

But when I do masternode status, I get:

{
   "vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
   "service" : "[::]:0",
   "status" : "Not capable masternode: Hot node, waiting for remote activation."
}

~~I think there is a problem with the new release.~~

Okay, I figured this out. The fix is simple.

Make sure you masternode start-alias from the 2.0.2.0 controller before you start the 2.0.2.0 masternode.

Another thing that you can do which works really well for me is to run your wallet locally as a controller and not a masternode. Then all of your remote nodes can be started with no issues. This is how i recommend people who use the coin-server.com hosting service for master nodes. Running in this manner tends to keep things problem free.