Quote from: StakeBox on September 30, 2016, 06:26:17 PM

Quote from: B1tUnl0ck3r on September 30, 2016, 02:49:42 PM

Quote from: cgt99 on September 28, 2016, 02:13:37 PM

I cant get masternode started with new version 2.1.3

Windows standalone MN on Windows 7 64bit.

"Not capable masternode: Could not connect to xx.xx.xxx.xx:51472"
Fully connected with other peers both In and Out.

Switching back to version 2.1.2.3 and masternode starts without issue:
"Masternode successfully started"

Didnt have this issue with the previos upgrades

I am in the same boat as cgt99. win7-64 same error message. I tried sync from scratch, no improvement.

my masternode.conf is empty (only the example), I didn't need to configure it with previous dnet version. If I switch back to the previous version, the masternode works perfectly.

However staking is working, it's specifically the masternode, the little lock icon never appears (tried to create new masternode too without success).

What should I do? any advices?

Hey guys, sorry I must have missed cgt99's message the other day, I can't stress enough how much better help you can get in skype or slack. I just played around for a minute setting up a local masternode, I saw the same error, I fixed it with the "masternodeaddr=XXX.XXX.XXX.XXX:51472" option in my darknet.conf. Give it a go and let us know how you get on with it.

I always had the line masternodeaddr=xxx.xxx.xxx.xxx:51472 in the darknet.conf

As i said it works perfect with the binaries from version 2.1.2.3

Fully connected with 18 inbounds an 8 outbound, canyouseeme.org reports succes for port 51472.

from debug.log:
CActiveMasternode::ManageStatus() - Checking inbound connection to 'xxx.xxx.xxx.xxx:51472'
CActiveMasternode::ManageStatus() - not capable: Could not connect to xxx.xxx.xxx.xxx:51472

I get the exact same result when trying version. 2.1.3 on second computer with other IP range and other router.

This isnt a conf issue i think.
What about that check wallet is doing for "inbound connection"?