Quote from: incognitoworker on March 15, 2017, 10:48:35 PM

Quote from: stonehedge on March 15, 2017, 07:54:08 PM

Quote from: incognitoworker on March 15, 2017, 05:14:32 PM

Quote from: defunctec on March 15, 2017, 05:09:39 PM

Quote from: incognitoworker on March 15, 2017, 04:27:55 PM

Quote from: stonehedge on March 15, 2017, 04:08:03 PM

Quote from: incognitoworker on March 15, 2017, 03:21:13 PM

I must have a config error, my node starts like normal, but go missing within one hour or less. This is the only masternode i run with this problem, anyone else experienced the same??

IW

Hi

This normally happens when your Throne server isn't contactable. Are you running it on a VPS?

No, its on a local machine where other masternodes also is running.
Since i only run one masternode of crown (for now) should i skip using the throne.conf and only use the "normal" conf??

IW

You can only host one Throne per IP address, if thats any help

Thnx, but i do only run one on that IP.
It starts up sucsessfully, but i get the "missing" status shortly after.

IW

Can you check that TCP port 9340 is open on your router? Your throne needs to be contactable on this port.

If your throne is starting ok, then i suspect that your other configs are correct.

Yes, port is open.
Now it says "Expired"
In crown.conf, should i use:
externalip:
throneadr:
masternodeadr:
??
I have setupt double digits of masternodes of various types, this is the only one arguing with me heh.
Can someone post a example of their working confs as this is frustrating me as it should work like all the others..

IW

https://github.com/Infernoman/Crown/releases/tag/fix-hot-throne

Grab the updated client from here
ignore the throne.conf since your running a local node
add this to your crown.conf
throne=1
throneaddr=(EXTERNAL IP:PORT)
throneprivkey=(crown-cli throne genkey)

(ignore the brackets)
and you should be good to go, if there's any issues just let me know. also with a local node it should startup automatically after the client has connected to the network successfully. you can watch the masternode status with "throne status" in the debug console, or crown-cli