Виделся на конфе с Кельвином, нормальный мужичок) привет ему передайте)))

you're on wrong chain, try this great instruction https://blog.espers.io/using-the-snapshot-d8eb6d1cb3f6
*use latest chain snapshot 706k instead of mentioned 704k can be found here https://mega.nz/#!lo0XATQR!VrztrfbX5fcW7jt0xcWNB-RgA7Ke992wa1sMdV2q6_I
hope this will help

externalip=[EXTERNALIP]
masternodeaddr=[EXTERNALIP:9399]

Make sure BOTH these calls have your current and correct external IP. Hope this helps.

This is my own personal das.conf copy/paste after a LOT of tweaking per references/help that I have had for over 2 weeks without a hitch along with daily payments when up/ENABLED 23+hours/day:

(Enter info in [] with correct info needed. NO spaces after=. # to ignore lines/command. addnode info from NovaExchange/updated often. exclude the begin/end lines on copy/paste info)

das.conf
------begin-----
rpcuser=[USER]
rpcpassword=[PASSWORD]
#rpcallowip=127.0.0.1
externalip=[EXTERNALIP]
rpcport=9399
#listen=1
port=9399
server=1
daemon=1
#staking=0
logips=1
maxconnections=50
masternode=1
masternodeaddr=[EXTERNALIP]:9399
masternodeprivkey=[MASTERNODEPRIVKEY]
#
addnode=107.174.69.220:9399
addnode=141.134.124.215:9399
addnode=142.217.120.113:9399
addnode=146.0.47.22:9399
addnode=154.16.7.191:9399
addnode=185.137.97.15:9399
addnode=185.209.20.97:9399
addnode=185.41.187.170:9399
addnode=193.71.119.49:9399
addnode=195.181.243.208:9399
addnode=212.47.243.63:9399
addnode=24.91.171.132:9399
addnode=35.184.44.214:9399
addnode=45.32.158.2:9399
addnode=45.32.169.164:9399
addnode=45.63.7.229:9399
addnode=45.76.245.31:9399
addnode=50.3.86.241:9399
addnode=51.15.37.50:9399
addnode=51.15.46.181:9399
addnode=52.161.110.178:9399
addnode=85.214.153.21:9399
addnode=93.206.113.45:9399
addnode=98.172.83.52:9399
addnode=98.226.11.139:9399
#
#
#addnode=94.19.244.216:9399
#addnode=185.51.247.100:9399
#addnode=93.206.113.45:9399
-----end-----


masternode.conf:
-------begin----
[MNalias] [EXTERNALIP:PORT] [masternodeprivkey] [collateral_output_txid] [collateral_output_index]
-----end-----


Regards,

c_p

right! i think i sorted out the issue, i deleted the Das file in Appdata and opened wallet... the wallet will now downloaded the block again.

the ENABLED status is no longer.

hmm... just found out that when i close and reopen the wallet my maternode status is still ENABLED.


it shows ENABLED even when my master node isn't started in the debug command.

So far as it should been...  What is the output when you are entering the 'masternode status' command on the debug window?

The masternode would need a fixed IP address ideally. But if you update your External IP and it is upto date and restart your wallet every time you make a change that should still work.
What kind of setup you have? Linux or Windows MN, hot/controlling wallet?
When you check the status of the MN, is it enabled?

masternode tab only work if you use masternode.conf

if you are using das.conf to create your masternode, use "all maternodes" and search for your ip

The easiest way to start masternode.

I did on Windows like this:

Settings das.conf in the wallet where you have 1000 coins.


Masternode.conf leave blank

In the console after synchronizing the wallet, you type "masternode star password".

And maybe you need to open port 9399.