Search results

Hi everyone, We've managed to get the MN up again. Indeed we needed to put the BLS Priv key in both the MN as client config. That was our mistake. This wasn't clearly mentioned in the wiki page. Thank you all for your assistance!

Hi qwizzie, That might just be it, we'll try that. In the wiki it isn't clearly mentioned that the bls private key should also be added to the client's dash.conf file. We'll follow up.

Hi Qwizzie, We didn't use brackets (""), and we're pretty sure everything was copied correctly. Prepared everything in notepad window so just copy pasted into the dash debug window. Yeah we're out of clues as well.

When executing the last command: protx register_submit ***

As clearly mentioned in our post, we've tried using the same keys, we've tried all possible combination and keep hitting that same error.

Hi Everyone, We've been struggling to start our masternode with the DIP003 protocol. With the last step as mentioned on this page we're getting the below error: bad-protx-key-not-same (code 16) (code -1) We're using the same address (newly generated) for both the owner and voting address...

Hi Devs, I've given this some thought: I have some concerns as to how dashcore currently checks it's external IP and availability through this address at the moment. This works fine for (master)nodes directly on the internet (say VPS'es), however for nodes behind routers (with NAT) this is an...

Hi Udjin, So I think there are some DNAT issues here to blame, apparently packets aren't recognized by the MN host, probably because the source IP is itself: MN --> Router [DNAT Back to MN] --> MN I've implemented a quick and dirty fix by adding our external IP to the host as a virtual...

Hi UdjinM6, I thought so too, but I've made sure port TCP/9999 forwards on both the internal and external interface. In my firewall I can actually see the count of "internal" connections that have been forwarded back to the node. Again, this worked fine before 0.12.1.

Hi Lynx, It runs every minute through cron, and outputs: "Invalid Masternode Status, cannot continue."

Wallet says successfull, mn says: $ dash-cli masternode status { "vin": "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )", "service": "190.1.2.3:9999", "status": "Not capable masternode: Could not connect to 190.1.2.3:9999" }

Here you go: $ dash-cli mnsync status { "AssetID": 999, "AssetName": "MASTERNODE_SYNC_FINISHED", "Attempt": 0, "IsBlockchainSynced": true, "IsMasternodeListSynced": true, "IsWinnersListSynced": true, "IsSynced": true, "IsFailed": false }

Hi All, Over the weekend we've tried it various ways, including with and without the externalip option, also with and without port. The remote wallet (with the 1000 dash) uses the masternode.conf as described in the documentation, and is started with "start masternode alias mn1" (if I remember...

To answer oaxaca: Without the port number, thus for example: externalip=190.1.2.3 I'm going to re-try with the latest release now, I will try to get some relevant debug output.

Yes, followed them step by step.

Dear Community, I've come here to find help with our masternode. Ever since the release of 0.12 we're unable to start our masternode. We've done a complete reinstall and used the previous dash.conf file. However we are unable start the MN. The error we're getting is: Not capable masternode...