• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Masternode Visible Status

DeathStryker

New member
Hello,

I've been a long time follower of Dash, and I recently had the opportunity to setup a few masternodes using Trezor. I followed tungfa's guide of setting up masternodes using Trezor, and it appears like I have been able to setup 2 out of the 3 nodes properly. However, the 3rd masternode setup gives me the following status info that is different from the others:

dashd version : 0.12.1.5
dashd up-to-date : YES
dashd running : YES
dashd uptime : 0 days, 11 hours, 20 mins, 33 secs
dashd responding (rpc) : YES
dashd listening (ip) : YES
dashd connecting (peers) : YES
dashd port open : YES
dashd connection count : 8
dashd blocks synced : YES
last block (local dashd) : 715799
(chainz) : 715799
(dash.org) : 715799
(dashwhale) : 715797
(masternode.me) : 715797 - no forks detected
dashd current difficulty : 464669.2699650239
masternode started : YES
masternode visible (local) : YES
masternode visible (ninja) : NO
masternode queue/count : 4229/4507
masternode mnsync state : MASTERNODE_SYNC_FINISHED
masternode network state : ENABLED
masternode last payment : never
masternode balance : 1000.000000000
sentinel installed : YES
sentinel tests passed : YES
sentinel crontab enabled : YES
sentinel online : YES


The rest of the setup looked fine in comparison to the other 2 masternode setups. Dash Ninja indicated that the 3rd masternode's port check was closed. I suspect these are related. I was hoping someone might be able to help me figure out how to fix the issue.

Thank you!
 
Back
Top