Search results

Yes, they're both ec2 t1.micro. The externalip in darkcoin.conf is correctly set. Maybe the devs can tell us what to do or if this is normal... :)

Do any of you have your masternode's IP address duplicated on the masternode list? I have both my nodes with duplicated self IP address entries... is it normal? masternode list { "112.175.123.94:9999" : 1, "54.238.156.138:9999" : 1, "54.215.215.6:9999" : 1, "142.161.23.40:9999"...

I had similar issue with some symbols in the password that generated errors in linux bash, so I moved to the laptop and changed it. Be sure not to include symbols that have meaning in the linux prompt. I had problems with ! , & and $. Oh and don't forget to backup wallet after password change...

Great news! Node up & running :) Congratulations on achieving this important milestone!

Well the root node Evan posted (23.23.186.131) is not available. Maybe we need to wait for a new update/information... Meanwhile I cleared the .darkcoind folder except wallet, conf and peers.

Ok. I'm also going to reject those. Thanks. Do you have any idea what that flag means?

Ubuntu on a amazon t1.micro (Linux ip-172-31-17-60 3.2.0-60-virtual #91-Ubuntu SMP Wed Feb 19 04:13:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux) I have an automatic script that updates the daemon from the link you posted so I thought maybe some internal update or something... Do you have you...

Hi, My masternode stopped connecting to other nodes. Was there any update to the daemon that I'm not aware of? Thanks. Before daemon restart: { "54.213.217.28:9999" : 0, "23.23.186.131:9999" : 0, "54.238.156.138:9999" : 0, "87.242.50.175:9999" : 0, "112.175.123.94:9999" : 0...