Hi,
I'm not sure i got my masternode right. I went for Method A, but when running ./craved masternode status on the mn i get.
{
"vin" : "CTxIn(COutPoint(528d71dc31, 0), scriptSig=)",
"service" : "pubIP:9999",
"status" : 9,
"pubKeyMasternode" : "Bzs4eQf7MwdwM2u5KRsutMXgQbUBrQRBaK",
"notCapableReason" : "Could not connect to PubIP:9999"
}
I was able to start MN from my wallet, and i can see TCP port 9999 traffic between my wallet IP and masternode ip. However, i still haven't reveived any rewards since 12 hours back. Which was my first reward, and appeared right after i've started the node.
What can i do to verify functionality?
Try ./craved masternode list. Check also if the port is open and the firewall disabled for this port. You can add this rule :
sudo iptables -A INPUT -p tcp --dport 9999 -j ACCEPT
./craved masternode list gives a list with a lot of nodes.
....
"d37127be953c1775aa9977a8e10bf5c390ff5776a950c4775b066b4f8d72e590-8" : "ENABLED",
"d37127be953c1775aa9977a8e10bf5c390ff5776a950c4775b066b4f8d72e590-9" : "ENABLED",
"d37127be953c1775aa9977a8e10bf5c390ff5776a950c4775b066b4f8d72e590-10" : "ENABLED"
}
service is listening on tcp port 9999
tcp 0 0 0.0.0.0:9999 0.0.0.0:* LISTEN
iptables -L shows nothing since i'm running a hardware firewall infront. TCP port 9999 is opened and the connection table is showing established connections (between 20-30 connections) inbound to my MN on TCP port 9999.
And i just verified that my wallet talked to my mn by restarting wallet, then tpcdumped traffic on MN filtering on windows wallet public IP.
Could it be a config setting i've screwed up?
Thanks for your help.