Before filing a new topic, please provide the following information.
Core DAppNode Packages versions
- bind.dnp.dappnode.eth: 0.2.6
- core.dnp.dappnode.eth: 0.2.47
- dappmanager.dnp.dappnode.eth: 0.2.42, branch: v0.2.43, commit: ec541936
- ipfs.dnp.dappnode.eth: 0.2.14
- vpn.dnp.dappnode.eth: 0.2.8, commit: f9a8743e
- wifi.dnp.dappnode.eth: 0.2.7
System info
- dockerComposeVersion: 1.25.5
- dockerServerVersion: 19.03.8
- dockerCliVersion: 19.03.8
- os: debian
- versionCodename: bullseye
- architecture: amd64
- kernel: 5.9.0-3-amd64
- Disk usage: 41%
From Prysm log
time=“2021-09-01 16:20:02” level=warning msg=“Could not determine if beacon chain started: could not get sync status: rpc error: code = Unavailable desc = connection error: desc = “transport: Error while dialing dial tcp 172.33.0.4:4000: connect: connection refused”: could not connect” prefix=validator
time=“2021-09-01 16:20:06” level=warning msg=“Could not determine if beacon chain started: could not setup beacon chain ChainStart streaming client: rpc error: code = Unavailable desc = connection error: desc = “transport: Error while dialing dial tcp 172.33.0.4:4000: connect: connection refused”: could not connect” prefix=validator
time=“2021-09-01 16:39:39” level=info msg=“Waiting for beacon node to sync to latest chain head” prefix=validator
I restarted the server, restarted the router. Does not help.
ping 172.33.0.4 is Ok
In the Prysm status I have:
-
Warning, the chain has not finalized in 4 epochs, which will lead to most validators leaking balances
-
beacon-chain.prysm.dappnode:4000/eth/v1alpha1
Connected
Syncing to chain head… -
Beacon Node Status
beacon-chain.prysm.dappnode:3500/eth/v1alpha1
Not Connected