This is the GorillaBucks.conf file, the masternode.conf is just supposed to contain the stuff previously posted now in red.
I believe that masternode.conf is not supported.
Yeah, i think that if the deamon is named like GorillaBand1, the .conf should be GorillaBand1.conf
Btw why are you starting the other wallet with listen=0?
Edit: There's this guide to setup a crave masternode, see if you can get anything out of it.
https://bitcointalk.org/index.php?topic=997356.msg11075558#msg11075558I'm following a DASH guide to to have one local wallet "control" two remote masternodes.
The listen=0 thing is explained there.
I think where I might be failing is the first few steps quoted below.
https://dashtalk.org/threads/reubens-start-multiple-masternodes-from-one-wallet-guide-start-many.4034/a. New wallet setup
Create a new address for each Masternode and encrypt the wallet. You do this by opening terminal and following the following instructions.
Enter the following command: "masternode genkey" and press ENTER.
You will see a long string of numbers and letters.
Please copy/paste this string to the new notepad file on your Desktop. This is the key you will need to verify your Masternode later in the process.
Enter the following command: "getaccountaddress 0" and press ENTER.
Please note that a normal Dash address is not the same as an address created in this manner!
IMPORTANT! Please backup the wallet now. Always backup the wallet BEFORE transferring any DRK!
Transfer 1000 DASH to each newly created address in one transaction.
Not really sure how address generation should be done for two addresses with this which could be why it's not working but every other step was followed to a T.
Also, someone said masternode.conf might not be supported which right now contains the below for the two rtemote nodes. If it's not supports how can it be supported ?
Current masternode.conf
GorillaBand1 :36480