web3labs/chainlens-free

Chainlens Startup Issue "An Error Occurred on Client"

Opened this issue · 5 comments

UsmArs commented

Hi there, I'm running besu Privacy Enabled network, I've installed the Chainlens or Sirato Explorer by following these instructions:

Step 1: Clone the Chainlens repository with this command:

git clone https://github.com/web3labs/chainlens-free.git

Step 2: Navigate to the Chainlens directory:

cd chainlens-free/docker-compose

Step 3: Start Chainlens using the following command in your terminal window:

NODE_ENDPOINT=http://<node_endpoint> docker-compose up

It runs only for a second or two and then the "An error occurred on client" error appears.

Moreover, one of my nodes is running on a multitenant network of besu, if you guys are aware when I connected to that node it showed me the interface but not the actual data, and when I connected to the normal node which is running on privacy enabled network only then it shows me the same error which I've mentioned in the upper section.

andrii-kl commented

Hi @UsmArs,
Did you test Explorer with another Client Node?

You can take any public networks to test if the problem in Explorer configuration. (Infura/Alchemy)

dlogvin commented

Can confirm that this error is happening to me, too. It's quite weird.

I'm on Mac OS, and I'm getting errors like:

2024/02/17 18:51:48 [error] 25#25: *116 connect() failed (111: Connection refused) while connecting to upstream, client: 172.16.239.1, server: , request: "GET /api/actuator/health HTTP/1.1", upstream: "http://172.16.239.4:8090/actuator/health", host: "localhost", referrer: "http://localhost/dashboard"

No idea where this IP (172.16.239.1) comes from, and neither 172.16.239.4.

IEndoKenji commented

I encountered the same error after testing with both my private and public networks (Alchemy).
Below are the nginx container logs:

[error] 28#28: *1 connect() failed (111: Connection refused) while connecting to upstream, client: <IP>, server: , request: "GET / HTTP/1.1", upstream: "http://<IP>:<PORT>/", host: "<IP>:<PORT>", referrer: "http://<IP>:<PORT>/"

[21/Feb/2024:07:37:45 +0000] "GET /api/actuator/health HTTP/1.1" 200 655 "http://<IP>:<PORT>/dashboard" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36"
dlogvin commented

I just tried deploying on Linux (Ubuntu), and I'm getting the same errors. The "An Error Occurred on Client" seems to be a front-end issue. Not sure if its affecting everyone.

  • 👍1
haerker commented

Can confirm that this error is happening to me, too. It's quite weird.可以确认这个错误也发生在我身上。这很奇怪。

I'm on Mac OS, and I'm getting errors like:我使用的是 Mac 操作系统，并且遇到如下错误：

2024/02/17 18:51:48 [error] 25#25: *116 connect() failed (111: Connection refused) while connecting to upstream, client: 172.16.239.1, server: , request: "GET /api/actuator/health HTTP/1.1", upstream: "http://172.16.239.4:8090/actuator/health", host: "localhost", referrer: "http://localhost/dashboard"

No idea where this IP (172.16.239.1) comes from, and neither 172.16.239.4.不知道这个IP（172.16.239.1）来自哪里，也不知道172.16.239.4来自哪里。

Hello, have you resolved it now? This IP address should be the bridged address of Docker in Linux. I am now facing the same problem.