Web3signer is missing - Nethermind doesn't sync - Coming back from service

Before filing a new topic, please provide the following information.

Hi, since my Dappnode has coming back from service, after it was powering off without any reason, I cannot install any web3signer anymore from the stakers menu. I have got several errors :

errorCall to stakerConfigSet
Today, 19:25:54
Reply: Global envs allowed are _DAPPNODE_GLOBAL_ACTIVE, _DAPPNODE_GLOBAL_INTERNAL_IP, _DAPPNODE_GLOBAL_STATIC_IP, _DAPPNODE_GLOBAL_HOSTNAME, _DAPPNODE_GLOBAL_UPNP_AVAILABLE, _DAPPNODE_GLOBAL_NO_NAT_LOOPBACK, _DAPPNODE_GLOBAL_DOMAIN, _DAPPNODE_GLOBAL_PUBKEY, _DAPPNODE_GLOBAL_ADDRESS, _DAPPNODE_GLOBAL_PUBLIC_IP, _DAPPNODE_GLOBAL_SERVER_NAME, _DAPPNODE_GLOBAL_CONSENSUS_CLIENT_MAINNET, _DAPPNODE_GLOBAL_EXECUTION_CLIENT_MAINNET, _DAPPNODE_GLOBAL_MEVBOOST_MAINNET, _DAPPNODE_GLOBAL_CONSENSUS_CLIENT_GNOSIS, _DAPPNODE_GLOBAL_EXECUTION_CLIENT_GNOSIS, _DAPPNODE_GLOBAL_MEVBOOST_GNOSIS, _DAPPNODE_GLOBAL_CONSENSUS_CLIENT_PRATER, _DAPPNODE_GLOBAL_EXECUTION_CLIENT_PRATER, _DAPPNODE_GLOBAL_MEVBOOST_PRATER. Got CONSENSUS_CLIENT_GNOSIS, EXECUTION_CLIENT_GNOSIS, FEE_RECIPIENT_GNOSIS
Error: Global envs allowed are _DAPPNODE_GLOBAL_ACTIVE, _DAPPNODE_GLOBAL_INTERNAL_IP, _DAPPNODE_GLOBAL_STATIC_IP, _DAPPNODE_GLOBAL_HOSTNAME, _DAPPNODE_GLOBAL_UPNP_AVAILABLE, _DAPPNODE_GLOBAL_NO_NAT_LOOPBACK, _DAPPNODE_GLOBAL_DOMAIN, _DAPPNODE_GLOBAL_PUBKEY, _DAPPNODE_GLOBAL_ADDRESS, _DAPPNODE_GLOBAL_PUBLIC_IP, _DAPPNODE_GLOBAL_SERVER_NAME, _DAPPNODE_GLOBAL_CONSENSUS_CLIENT_MAINNET, _DAPPNODE_GLOBAL_EXECUTION_CLIENT_MAINNET, _DAPPNODE_GLOBAL_MEVBOOST_MAINNET, _DAPPNODE_GLOBAL_CONSENSUS_CLIENT_GNOSIS, _DAPPNODE_GLOBAL_EXECUTION_CLIENT_GNOSIS, _DAPPNODE_GLOBAL_MEVBOOST_GNOSIS, _DAPPNODE_GLOBAL_CONSENSUS_CLIENT_PRATER, _DAPPNODE_GLOBAL_EXECUTION_CLIENT_PRATER, _DAPPNODE_GLOBAL_MEVBOOST_PRATER. Got CONSENSUS_CLIENT_GNOSIS, EXECUTION_CLIENT_GNOSIS, FEE_RECIPIENT_GNOSIS
at ComposeServiceEditor.setGlobalEnvs (/usr/src/app/webpack:/@dappnode/dappmanager/src/modules/compose/editor.ts:189:17)
at /usr/src/app/webpack:/@dappnode/dappmanager/src/modules/release/getRelease.ts:54:13
at Generator.next ()
at fulfilled (/usr/src/app/index.js:416546:58)
at processTicksAndRejections (node:internal/process/task_queues:95:5)

{
“stakerConfig”: {
“network”: “gnosis”,
“executionClient”: {
“status”: “ok”,
“dnpName”: “nethermind-xdai.dnp.dappnode.eth”,
“avatarUrl”: “/ipfs/QmcVMsV3QYhTK1R7DwjBQ44hafxee9m3HVvda9Pv2F3PiX”,
“isInstalled”: false,
“isUpdated”: false,
“isRunning”: false,
“isSelected”: true
},
“consensusClient”: {
“status”: “ok”,
“dnpName”: “teku-gnosis.dnp.dappnode.eth”,
“avatarUrl”: “/ipfs/QmWayujdokAffcX6hXTcGuaTQDBK7T41gEgaHbR99b64DD”,
“isInstalled”: true,
“isUpdated”: true,
“isRunning”: true,
“isSelected”: true,
“graffiti”: “validated_by_GeminiCrickETH”,
“feeRecipient”: “0x4AA9833E5D1aA406880D291E3ab7aa284f6E8e86”,
“checkpointSync”: “https://checkpoint-sync-gnosis.dappnode.io
},
“enableWeb3signer”: true
}
}

Is there a way to reset my Dappnode to factory defaults to start from scratch ?

Core DAppNode Packages versions

  • bind.dnp.dappnode.eth: 0.2.6
  • dappmanager.dnp.dappnode.eth: 0.2.59, commit: 26522964
  • https.dnp.dappnode.eth: 0.2.1
  • ipfs.dnp.dappnode.eth: 0.2.18
  • wifi.dnp.dappnode.eth: 0.2.8
  • wireguard.dnp.dappnode.eth: 0.1.2

System info

  • dockerComposeVersion: 1.25.0
  • dockerServerVersion: 20.10.5+dfsg1
  • dockerCliVersion: 20.10.5+dfsg1
  • os: debian
  • versionCodename: bullseye
  • architecture: amd64
  • kernel: 5.10.0-18-amd64
  • Disk usage: 7%

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.