cd /path/to/chia
chia start farmer
chia plots check -n 30
chia plots add -d /path/to/plots
chia farm summary
chia init
.chia plots create -f farmer_key -p pool_key
, inserting the farmer and pool keys from your main machine. Alternatively, you could copy your private keys over by using chia keys add
, but this is less secure. After creating a plot, run chia plots check
to ensure everything is working correctly.~/.chia/mainnet/config/ssl/ca
to be accessible by your harvester machines; you can share the ssl/ca
directory on a network drive, USB key, or do a network copy to each harvester. Be aware that major updates might need you to copy the new ca
contents. Verify that the harvester does not report SSL errors on connections attempts.NOTE: For step 7, you are using a copy of your /ca
directory from your main machine temporarily. DO NOT replace the /ca
folder on your harvester. Put the /ca
directory into a temp folder on your harvester. You're going to show your harvester these files temporarily and then you can delete the /ca
directory in your temp folder.
chia stop all -d
chia init -c [directory]
on your harvester, where [directory] is the copy of your main machine /ca
directory that you put in a temp folder. This command creates a new certificate signed by your main machine's CA.~/.chia/mainnet/config/config.yaml
file in each harvester, and enter your main machine's IP address in the remote harvester
's farmer_peer section (NOT full_node
).EX:
harvester:
chia_ssl_ca:
crt: config/ssl/ca/chia_ca.crt
key: config/ssl/ca/chia_ca.key
farmer_peer:
host: Main.Machine.IP
port: 8447
chia start harvester -r
and you should see a new connection on your main machine in your INFO level logs.chia stop harvester