Sorry, something went wrong. Please report this issue to our support team so we can investigate and resolve the problem. [Report Issue]

[krzysiekknap]

I have not been able to run the node for few days. Is this due to work on Shardeum:Atomium?

[rohitsenindia]

same issue face after install node

[anhtudo97]

Any way to bypass this issue

[Cybertr0n313]

im also having this issue. been running a node for months

[basiof]

Same here!

[basiof]

[sskanthy]

Same for me.

[MMatias1972]

Hello, I got same problem, but I guess it is RPC connections, if you try check Chainlist it's off

[selver-sku]

Same for me...

[canhcanh]

same for me

[kaimano]

Same here, for many days now

[stewfarq]

Same for me. The error seems to have appeared within the last week or so. I have the latest version of the node. operator-cli status returns...

/home/node/app/cli/build/src/utils/fetch-network-data.js:132 throw new Error('Unable to fetch list of nodes in the network'); ^

Error: Unable to fetch list of nodes in the network at getNewActiveNode (/home/node/app/cli/build/src/utils/fetch-network-data.js:132:15) at runNextTicks (node:internal/process/task_queues:60:5) at listOnTimeout (node:internal/timers:538:9) at process.processTimers (node:internal/timers:512:7) at async fetchDataFromNetwork (/home/node/app/cli/build/src/utils/fetch-network-data.js:67:9) at async fetchStakeParameters (/home/node/app/cli/build/src/utils/fetch-network-data.js:299:25) at async Promise.all (index 0) at async /home/node/app/cli/build/src/node-commands.js:222:153

[kaimano]

yes, same for me

[toppo1986]

same is mine

[fl0wm0ti0n]

Same, also after reinstalling everything

[batyrshinas]

Same problem after try upgrade and change network to Shardeum Atomium

[dxhod]

Have the same issue

[innowile]

I'm facing this, is it generally or just me

[Psykepro]

same here