Hosting Execution client on a Different Machine

Hosting your own execution client on a different machine than where your beacon-chain and validator resides, can allow some extra modularity and flexibility.

On the execution client machine, edit your eth1.service unit file.

sudo nano /etc/systemd/system/eth1.service

Add the following flag to allow remote incoming http and or websocket api requests on the ExecStart line.

If not using websockets, there's no need to include ws parameters. Only Nimbus requires websockets.

Geth

--http.addr 0.0.0.0 --ws.addr 0.0.0.0
# Example
# ExecStart       = /usr/bin/geth --http.addr 0.0.0.0 --ws.addr 0.0.0.0 --http --ws

OpenEthereum (Parity)

Besu

Nethermind

Reload the new unit file and restart the execution client.

sudo systemctl daemon-reload
sudo systemctl restart eth1

On the separate machine hosting the beacon-chain, update the beacon-chain unit file with the execution client's IP address.

Lighthouse

# edit beacon-chain unit file
nano /etc/systemd/system/beacon-chain.service
# add the --eth1-endpoints parameter
# example
# --eth1-endpoints=http://192.168.10.22

Nimbus

Teku

Prysm

Lodestar

Reload the updated unit file and restart the beacon-chain.

sudo systemctl daemon-reload
sudo systemctl restart beacon-chain