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=
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
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).