Ive did this i have 1 question
the desire.conf looks like this
masternode=1
masternodeprivkey=7qt9zSJWu******G943kK825pnuGPwEDZRjN7ohUdmJUynSK5Qc
externalip=78.204.***.214
then you said
at least, the following data:
rpcuser=someuser ->ive set the username
rpcpassword=somepass > set pass
server=1 > let it as is
rpcport=9918> 9919
rpcconnect=127.0.0.1 -> my IPV4
still sentiel says Invalid Masternode Status, cannot continue.'
Im not sure if your guide is for the Hot wallet version
You should apply these steps to
whichever wallet the masternode is running on, either if it is hot wallet or cold wallet. If it is a hot wallet, then simply apply it to the wallet (you should have only 1). If it is a cold wallet, apply it to the wallet the MN is running on.
I am assuming the masternode wallet and sentinel are running in the same machine. Then:
* rpcport CANNOT be 9919, that's the port for the masternode, not the rpc. I really recommend you to set it to 9918.
* rpcconnect must be the IP where the masternode is running on. If it is the same machine where sentinel will run, it should be 127.0.0.1, not your IPv4
I tried asking that above too but mninfo ignored me.
We need clarification on what instance types need to have sentinel running.
Ignoring someone is kind of harsh when I'm doing this out of self-will and expecting nothing, don't you think it is quite more possible that after being +16h without sleeping, 7h of which I have been doing this standalone sentinel, I might have overread your question? Just a wild thought, I might be wrong
You should apply these steps to
whichever wallet the masternode is running on, either if it is hot wallet or cold wallet. If it is a hot wallet, then simply apply it to the wallet (you should have only 1). If it is a cold wallet, apply it to the wallet the MN is running on.