[ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN

[cryptohunter]

Which vps makes it the easiest to setup the masternodes?

[jk9694]

Which vps makes it the easiest to setup the masternodes?

I provide fully managed nodes, so you just run your local wallet as a controller.  No setup of the nodes required.  Just a few bits of information needed and 2$ for 30 days of hosting.  PM me is you would like more details.

[kokokoin]

All my v1.0.2 masternodes are stuck at block 70751. But they continue to generate rewards.

[borris123]

All my v1.0.2 masternodes are stuck at block 70751. But they continue to generate rewards.

mine stuck at different ones as well. I think its just a visual thing needs fixing tho

[bathrobehero]

All my v1.0.2 masternodes are stuck at block 70751. But they continue to generate rewards.

mine stuck at different ones as well. I think its just a visual thing needs fixing tho

It's definitely not just a visual issue. It's just takes time for masternode payments to stop.

[djselery]

had the same problem. stuck at 70751. restarted and i got a firewall issue. allowed it through the firewall and all is well for now... hmm.

[borris123]

All my v1.0.2 masternodes are stuck at block 70751. But they continue to generate rewards.

mine stuck at different ones as well. I think its just a visual thing needs fixing tho

It's definitely not just a visual issue. It's just takes time for masternode payments to stop.

got 1 stuck at 71257 and it is currently on block 71836, just got a payment from it. thats alot of blocks inbetween to say its meant to stop?

[waffles99]

Running multiple mp-hosting nodes

upgraded to 1.0.2.0 when released, including deleting .darknet folder except for conf file

Still receiving payments, only had to send start-alias command for 1 node with expired status

1 node was status missing this morning, has since auto-resolved

tor nodes broadcasting an externalip onion address running without issue

[danonthehill]

No problems with my MN.

[bathrobehero]

Yesterday I resynced a bunch of my masternodes and almost all of them are stuck now with plenty of connections on a bunch of different blocks (71406, 71411, 71460, etc).

But masternode count is still high so I'm not sure if they will expire or actually working.

Both of my local non-masternode wallets also got stucked on different blocks and they're not receiving transactions unless I restart the wallet and it syncs the last few hours.

[EleanorZ]

1 node was status missing this morning, has since auto-resolved

Is there a trick to resolving missing nodes "on purpose"? I stopped and restarted mine, synced them, all MNs successfully enabled, then two hours later all were missing. Start-missing, all successfully enabled, then two hours later all were missing again. This has repeated for the last 24 hours. Have received one payment so obviously things are working sometimes...just not all the time.

[borris123]

1 node was status missing this morning, has since auto-resolved

Is there a trick to resolving missing nodes "on purpose"? I stopped and restarted mine, synced them, all MNs successfully enabled, then two hours later all were missing. Start-missing, all successfully enabled, then two hours later all were missing again. This has repeated for the last 24 hours. Have received one payment so obviously things are working sometimes...just not all the time.

go back to 1.0.1.0 version till they fix it

[ainv42]

1 node was status missing this morning, has since auto-resolved

Is there a trick to resolving missing nodes "on purpose"? I stopped and restarted mine, synced them, all MNs successfully enabled, then two hours later all were missing. Start-missing, all successfully enabled, then two hours later all were missing again. This has repeated for the last 24 hours. Have received one payment so obviously things are working sometimes...just not all the time.

go back to 1.0.1.0 version till they fix it

I also see the error after the transition to the new version. But it is not necessarily after the 80k block?

[cryptohunter]

where are the devs lately?

[Mashugina71]

Mine stopped again at 72257. Used wallet repair and reindexed blocks. Still going since then so maybe that will fix it (shrug)

[bathrobehero]

Would be nice if the devs would chip in on the issue.

[4x13]

Would be nice if the devs would chip in on the issue.

Yes it would.. Sometimes it takes sometime to work out the issue.  I am not saying this is the final fix, but go with me here as this works for myself and a few others we have tested this on;

on wallet version 1.0.2.0;

in your darknet.conf file located in your masternode; add this line;

externalip=<put your masternode ip address here>

save and do a sudo reboot

then make sure your daemon is restarted and you should be good. If this isn't working for your, let us know, so we can continue to research the issue. please give it an hour or so to see if this works.

Thanks

EDIT: Also make sure you do a 'masternode start-alias <Mastnernode name> <your wallet pass phrase>

[OKorator]

Is there an API or similar to monitor voting via Webpage?

[4x13]

Is there an API or similar to monitor voting via Webpage?

Not yet, it is in development at the moment

[bathrobehero]

Would be nice if the devs would chip in on the issue.

Yes it would.. Sometimes it takes sometime to work out the issue.  I am not saying this is the final fix, but go with me here as this works for myself and a few others we have tested this on;

on wallet version 1.0.2.0;

in your darknet.conf file located in your masternode; add this line;

externalip=<put your masternode ip address here>

save and do a sudo reboot

then make sure your daemon is restarted and you should be good. If this isn't working for your, let us know, so we can continue to research the issue. please give it an hour or so to see if this works.

Thanks

EDIT: Also make sure you do a 'masternode start-alias <Mastnernode name> <your wallet pass phrase>

Thank you for acknowledging the issue.

But your workaround is not helpful for non-masternode wallets behind a firewall. And some people have their masternodes runnig with dynamic IPs.

Also, the number of active masternodes (masternode count) is fluctuating quite heavily.

I'm hoping you guys can track and fix the issue.

Edit: I have two recently restarted (eg. 10 minutes ago) and synced wallets on the same block height showing different masternode counts (416 vs 426 at block 72338 with 8 peers connected each).