✅|ANN| 🌍DESIRE |NeoScrypt| |🔨MasterNodes🔨|

I ran into some problems with my VPS Desire masternode, I've set it up according to this howto ==> http://www.bittcoinwatch.com/how-to-setup-desire-masternode/ with a 4 GB Swapfile and opened the ports in the firewall. According to the masternode status command (on both the vps and windows local wallet) the masternode is working.

For some reason it seems when I close my local windows wallet, after a while the masternode stops. When I start my windows wallet (after 2 hours) it looks like my masternode starts again. According to the masternode list in my wallet the node starts every morning when I check my status. This doesn't seem right and is perhaps the main cause that there are no any payouts to my DSR wallet. In my wallet D8bncVdYyhGprL8nJpt63ks9QTvaGGvvg8 there is an exact amount of 1000.00 DSR so this seems to be ok. The VPS masternode is at 185.92.222.249:9919. I've reinstalled the VPS today and started it 10 hours ago. Just when I came back a hour ago and check the status, the windows wallet told me the masternode was 00h:01m:06s active and it should be a least 9 hrs.

Accoring to my information this should not be happening and perhaps I'm doing something wrong, any idea how to fix this ?

I have done the same and used the same guide... However I haven't done every steps from it.

On my local windows wallet, the desire.conf file is blank and only the masternode.conf file is edited.
On my VPS wallet, only the desire.conf file is edited, the masternode.conf untouched.

You definitely don't want to put the 'masternode=1' in your local wallet desire.conf file...

I would suggest to delete everything from the desire.conf file on your windows local wallet.

Thanks for the info, just checked and on my windows system there is a desire.conf with masternode=1. I've comment out everything and started the wallet. On the masternode tab it now shows that masternode is up for 12h (just started my windows system) so this looks good

!. On the masternode itself useing ./desire-cli masternode list it shows the status is WATCHDOG_EXPIRED. It shows the same on the local wallet. Does this mean I need the restart the sentinal ? Or is this optional and doesn't do anything for the masternode and payouts ?

That is a bit trickier question. When I followed that guide, I have done the sentinel a bit differently.
I have installed tux and started Sentinel on a tux process where it is running in the background all the time.

Try the following after followed the Linux part of the guide and installed Sentinel.

sudo apt install tmux htop
tmux new -s sentinel
cd ~/.desirecore
./sentinel-lin64

Once sentinel is running, wait a few minutes and press CTL+B then D. That should send the session to the background and you are back on the terminal.

Type htop to see all the process running on the VPS. You should see 'tmux sentinel' in that list. Your status will switch to ENABLED within 30 minutes.

But I read somewhere in the Discord, if the uptime is increasing then you should get reward regardless of the status.. I haven't tested it, looks better with Enabled.

I didn't get around to update the VPS, but it seems the first payment is arrived yesterday evening late. Today there is a notification "Not enough compatible inputs to anonymize 1 000.0000000 DSR wil anonymize 5.00000 instead" in the local windows wallet. Is this message there because the wallet now contains 1005 DSR ??

That message looks like if you try to enable the private/anonymity/coin mixing function as you would need to have the double amount of coin to make it work.... Don't enable this feature, it doesn't work not even for Dash as you don't even need it to run a masternode. It won't affect anything.