** edit
I did a fresh install of the dappnode on a zotac xbox ci662. During the install, there was a failure on the software update step and the installer allowed me to skip to the install grub boot loader on hard disk step and finish up the installation.
Afterwards I connected to dappnode through the wifi hotspot and attempted to open the installer tab as well as the packages tab which failed with an error
**
Call to fetchCoreUpdateData
Error: dappGet could not resolve request core.dnp.dappnode.eth@*, error on aggregate stage: Error: getaddrinfo EAI_AGAIN web3.dappnode.netweb3.dappnode.net:443
at exports.XMLHttpRequest.request.onreadystatechange (/usr/src/app/webpack:/app/node_modules/ethers/utils/web.js:85:1)
at exports.XMLHttpRequest.dispatchEvent (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:591:1)
at setState (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:610:1)
at exports.XMLHttpRequest.handleError (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:532:1)
at ClientRequest.errorHandler (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:459:1)
at ClientRequest.emit (events.js:189:13)
at TLSSocket.socketErrorListener (_http_client.js:392:9)
at TLSSocket.emit (events.js:189:13)
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
** edit
I did a fresh install of the dappnode on a zotac xbox ci662. During the install, there was a failure on the software update step and the installer allowed me to skip to the install grub boot loader on hard disk step and finish up the installation.
Afterwards I connected to dappnode through the wifi hotspot and attempted to open the installer tab as well as the packages tab which failed with an error
**
Call to fetchDirectory
Error: Error: getaddrinfo EAI_AGAIN web3.dappnode.netweb3.dappnode.net:443
at exports.XMLHttpRequest.request.onreadystatechange (/usr/src/app/webpack:/app/node_modules/ethers/utils/web.js:85:1)
at exports.XMLHttpRequest.dispatchEvent (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:591:1)
at setState (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:610:1)
at exports.XMLHttpRequest.handleError (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:532:1)
at ClientRequest.errorHandler (/usr/src/app/webpack:/app/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:459:1)
at ClientRequest.emit (events.js:189:13)
at TLSSocket.socketErrorListener (_http_client.js:392:9)
at TLSSocket.emit (events.js:189:13)
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
Thanks for reporting both Call to fetchDirectory and Call to fetchCoreUpdateData error logs, but in order to have a look at them, can you please add some context?
Are you facing any issues using the UI or any DAppNode Packages?