Post
Topic
Board Announcements (Altcoins)
Re: Project Interzone - Blockchain Social Engine - UPDATE TO 1.5
by
Onetrack
on 12/10/2017, 16:19:55 UTC


Quote

you can remotely activate the masternode with masternode.conf using the command line...
here are the steps:
- close the gui wallet
- add masternode.conf file to %appdata%\roaming\interzone
- open windows cmd and navigate to the interzone binaries file (using cd)
- repeat the above step
- from the first cmd window run interzone.exe
- optional: in case your wallet is locked with password from the second cmd: interzone.exe walletphrase "your_password" 300
- from the second window run interzone.exe masternode start-alias YOUR_ALIAS_NAME
Done!

if you want to see your mn in gui on the masternode list:
- from the second cmd: interzone-cli.exe stop
- close both cmd and rename masternode.conf to other  name

now you can open the gui version. GL!



gui version crashes if there is a masternode.conf file
editing the interzone.conf file with my local pc details and removing masternode.conf results in the gui loading - at first I was getting a connection error to my pc - introduced port forwarding - now getting:

06:41:24

masternode start


06:41:24

not capable masternode: Could not find suitable coins!

this is incorrect as 5k coins were allocated to this wallet last night and its been confirming all night long.

tried the cli version - get even less results.

Even trying both ports after introducing port forwarding to my system:
not capable masternode: Could not connect to 70.xx.xx.xx:55675 (and the other port as well..)

removed the peers.dat file as some say this could help with this on chaincoin, no go.

Following the instructions to a t and its not happening. Certainly not my first MN setup, but proving to be the most difficult.




Almost there,

not capable masternode: could not connect to xx.xx.xx.xx(mypublicip):11994

Port forwarding for 11994 both tcp/udp is wide open, firewall is off.

can't connect..... it auto setup rules in windows firewall for ALL ports allowed for both tcp/udp just refuses to connect.