Setting up an Erigon provider

Becoming an Erigolem provider

Here we describe an installation script which should make the whole process of becoming an Erigolem provider fun and smooth. The script is prepared for Ubuntu 18.04 or later and should work on other Linux distributions after some modifications.

This is an experimental setup. It's not intended to be run on personal computers because:

  • It creates a separate user which will run the provider daemon,

  • It installs the NGINX web server and certbot,

  • Optionally, it generates a Let's Encrypt certificate and sets certbot to remind you about certificate renewals,

  • It disables all runtimes for yagna other than ya-runtime-erigon.


  • Ubuntu 18.04 or later

  • Root privileges

  • Public IP address or a DNS name

  • Ability to open a port for the Erigon service

By default nginx's reverse-proxy is listening on the standard Erigon port 8545. You need to open this port for incoming traffic. If you wish your Erigolem service to be available on a different port number (e.g. because 8545 cannot be opened), you need to edit the installation script.

Example patch changing 8545 to 9999

diff --git a/ b/
index 2bb4de9..41ad5e2 100644
--- a/
+++ b/
@@ -161,8 +161,8 @@ http {
server {
- listen 8545${ERIGON_USE_SSL:+ ssl http2};
- listen [::]:8545${ERIGON_USE_SSL:+ ssl http2};
+ listen 9999${ERIGON_USE_SSL:+ ssl http2};
+ listen [::]:9999${ERIGON_USE_SSL:+ ssl http2};
server_name $ERIGON_HOSTNAME;
@@ -240,7 +240,7 @@ mkdir -p "${ERIGON_USER_HOME}/.local/share/ya-runtime-erigon"
cat >"${ERIGON_USER_HOME}/.local/share/ya-runtime-erigon/ya-runtime-erigon.json" <<EOF
- "public_addr": "https://${ERIGON_HOSTNAME}:8545",
+ "public_addr": "https://${ERIGON_HOSTNAME}:9999",
"data_dir": "${ERIGON_DATADIR}",
"passwd_tool_path": "htpasswd",
"passwd_file_path": "/etc/nginx/erigon_htpasswd",

Parameters for the script

Script behavior can be modified by the following environment variables:


default value




OS user the service is running on



Erigon data directory. Each chain data is collected in the subdirs


HAS TO be set before running the installation script, e.g.


Test this script without nagging letsencrypt services. If not set, (the inverse) ERIGON_USE_SSL is set


Not needed when ERIGON_DISABLE_SSL is set. Email address for the certbot to remind of SSL certificate renewal.

Running the script

  1. Download the installation script on the installation machine

    curl -sSfL -o \
  2. Review and edit the script if needed

  3. Execute the script

    Example script invocation (provider values for your environment)

    sudo env ERIGON_USER=golem \ \
    ERIGON_DATADIR=/data/erigon \

    During the installation you will be asked to:

    • Accept Golem's licence terms,

    • Provide the name for the provider node,

    • Provide the subnet the node will be subscribed to,

    • Provide your wallet address,

    • Provide the desired price per hour (in GLM).

  4. Make sure the port is opened

    It depends on how your machine was provisioned, but you might need also to allow ingress connections on the firewall.

    sudo ufw allow 8545/tcp

Check installation

After a successful installation, verify that the service is running.

sudo systemctl status golem

You can also check the logs of the running service

sudo journalctl -u golem -e