gobitfly/eth2-beaconchain-explorer

Connect to local besu client failed: Connection Refused

meijiesky opened this issue · 0 comments

Describe the bug
We are comparing BlockScout and Beaconchain explorers and want to use one of them in our project.
We have a private local network with one/four besu clients and we want to use explorers to show blocks/txs in the network. I modified the config file and the shell script because I don't need to connect to testnet/mainnet. However, it was very hard to get it working with Beacon. If so, we have to choose BlockScout then.

To Reproduce
Steps to reproduce the behavior:

  1. comment out code below "Spin up a local ethereum testnet" in main.star
  2. modify provision-explorer-config.sh to set CL_PORT and EL_PORT to my besu rpc port "8545"
  3. (hacky) modify provision-explorer-config.sh to set clConfigPath to empty and name to mainnet because running the script failed due to the failure to call eth/v1/config/spec for besu client
chain:
  clConfigPath: ''
  name: 'mainnet'
  elConfigPath: 'local-deployment/elconfig.json'
  1. kurtosis run --enclave my-testnet .
  2. bash provision-explorer-config.sh
  3. docker compose up

Expected behavior
All containers running properly.

Screenshots
All containers exited and the logs are as follows.
Screenshot 2023-12-29 at 16 58 46

Versions (please complete the following information):

  • OS: macOS x86 14.1
  • Beacon: v1.48.1
  • Besu: commit be5cc68b6069ca2f718d08c95994e1a764576391