Regarding the fact that there are multiple servers in the LAN, can only

Support
, , ,
41

ping ****

Is it too high?

42

image

43

Your ping is too high. I suggest it generally not exceed 5ms.

Moreover, the traffic between the farm and the nodes will be very large, and your router also needs to be able to support this traffic.

My farm connection node requires about 700M bandwidth. Although it only uses 50M most of the time, it sometimes uses a lot of bandwidth.

1 Like
44

We have what we have, and we will have to survive with it.

45

60ms is obviously not the ms in the LAN. The LAN should not be so high.

1 Like
46

On one node-farmer pair, I managed to set up farmer interaction with a remote node. When I try to run the second pair in another network according to the same exact pattern, on a farmer I get an error:

Sep 14 19:45:52 lenovo7 subspace-farmer[41607]: Error: Networking or low-level protocol error: Connection rejected with status code: 429
Sep 14 19:45:52 lenovo7 subspace-farmer[41607]: Caused by:
Sep 14 19:45:52 lenovo7 subspace-farmer[41607]:     Connection rejected with status code: 429
Sep 14 19:45:52 lenovo7 systemd[1]: subspacefarm.service: Main process exited, code=exited, status=1/FAILURE
Sep 14 19:45:52 lenovo7 systemd[1]: subspacefarm.service: Failed with result 'exit-code'.

Please tell me how to fix it?

47

Please make sure your node version is consistent with the farm version, and make sure you have added the following parameters:
–rpc-methods unsafe
–rpc-external
–rpc-cors all
–no-private-ipv4 \

48

Please send the startup parameters of your node and farm

49

Right, the versions are different… :man_facepalming: Give me 30 minutes…

50

Hmm, now I am trying to connect external farmer to node with it’s local farmer, and the node says
Sep 14 23:50:06 lenovo25 subspace-node[3371648]: 2023-09-14 23:50:06 Too many connections. Please try again later..

p.s. --rpc-max-connections="200" parameter on node helped.

51

Believe it or not, only six weeks later, I finally got round to testing this out in the last few days. If we leave the below out of the compose we end up with 403 errors.

"--rpc-cors", "all",

Node

Denied request: HTTP header: `host` value: `subspace-node:9944` verification failed

Farmer

INFO subspace_farmer::commands::farm: Connecting to node RPC url=ws://subspace-node:9944
Error: Networking or low-level protocol error: Connection rejected with status code: 403

Caused by:
    Connection rejected with status code: 403

I agree that I’ve only seen CORS errors in a browser before but it is significant to the way the containers are communicating.