Configure farmer-only at home and full-node on VPS

[Ealrann]

Hello,

My internet connection is slow (something like 10Mb/s), and running a full node makes it bad (regular ping spikes).
So I'm trying to put the full node on a VPS, and keep the farmer/harvesters at home.

The configuration looks rather simple:

# Home Farmer
farmer:
  full_node_peer:
    host: <vps address>
    port: 8444

# VPS node
full_node:
  farmer_peer:
    host: <home address>
    port: 8447

So far, so good, but it's too early to be sure everything is working.

Here my questions:

1. In this situation, who needs the private key? I guess definitely the Farmer, but what about the Full node?
2. Is an up-to-date wallet necessary to farm with plotnft? if so, where (farmer side or node side?)
3. Configuring the farmer address in the full node configuration looks not necessary. Is there any benefit doing it? Would the full node prioritize this farmer, or something like that?
4. Does anyone made a similar configuration? Any tip?

[loppefaaret]

my tip would be to run both the node and farmer on the vps, and then having your home be a remote harvester
i cant answer for if the node or the farmer can handle not having the keys
plotNFT farming is depending on the owning wallet is synced passed the last time you changed the plotNFT

[cross]

I am running multiple systems as @loppefaaret describes, using https://github.com/Chia-Network/chia-blockchain/wiki/Farming-on-many-machines as a guide. I think it would work for you, and if you wanted you could have the farmer on the vpn just not have any plots. Then you'd get about the same. A harvester on the system at home passing data to the farmer on the vps.
(I'm not sure the bandwidth needed between farmer and harvester, someone else would have to answer that.)

[Ealrann]

Indeed, I thought of that at beginning, but since I have many harvesters, the bandwidth appears to be lower between farmer<->fullnode than between farmer<->harvesters. That's why I wanted to try this setup.
Also, I feel better about security since my private key is not on internet, only at home in a server I fully control.

[Ealrann]

Since I run this setup for few days now, I can partially answer my questions:
It works, I won a bloc, and pool farming with plotnft works too.

1. Private key should be on the farm. No need on full node.
2. Just in case, I have a wallet working on farmer side. But even when I disable it, farming still works.
3. No answer yet, I'd like developers make a full doc about the configuration.

[loppefaaret]

thank you for returning, and answering your own questions

on 3: it should not make any difference as far as im aware, as it is the farmer that connects to the node - the node just services the farmer

[Ealrann]

Ok, thanks for the answer. I got the same feeling

[wiryonolau]

Did your setup break on 2.0.0 ?

[Ealrann]

Home Internet is not slow anymore (I got optic fiber), I'm not using a deported node anymore so v2.0.0 went smooth for me

[wiryonolau]

Can somebody help me with this ? Perhaps some tips on which file need to change ?

Can this be done
#9615 (comment)

[BrandtH22]

If you are still experiencing the issues it is recommended to upgrade to the latest version of chia. Please download it from here: https://www.chia.net/downloads/

Since this issue has been open for a number of years without additional comments, we will be closing this ticket but if we have closed this ticket in error do not hesitate to reach out to us again with any followup questions, comments, or if the issue persists after an update.

Please note that upgrading major versions of chia generally requires the config.yaml to be recreated using these steps:
1. Stop chia
2. Rename the config or move it to a different directory
3. In CLI run chia init
4. Copy any custom settings from the old config to the new (plot drive directories, pool info, trusted node info, etc) - be careful here as yaml is very picky about formatting including those leading spaces
5. Start Chia

The best place to reach our support team is on Discord (https://discord.gg/chia) or by reopening this ticket.