The node seems to be offline

SILO Node Operators
1

Hello i need some help, the node seems to be offline.

This is the docker error message:

2025-03-08 01:49:50 2025-03-08T00:49:50Z ERROR contact:service ping orbital failed {“Process”: “storagenode”, “Orbital ID”: “1dkRxqhU46NfjV1xJZrxnt8RwWGK2uAas1jtncvZoj4s8HVVK4”, “attempts”: 8, “error”: “ping orbital: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 89.98.158.152:28967: connect: connection timed out”, “errorVerbose”: “ping orbital: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 89.98.158.152:28967: connect: connection timed out\n\tsilos3.com/silo/storagenode/contact.(*Service).pingOrbitalOnce:209\n\tsilos3.com/silo/storagenode/contact.(*Service).pingOrbital:157\n\tsilos3.com/silo/storagenode/contact.(*Chore).updateCycles.func1:87\n\tsilos3.com/common/sync2.(*Cycle).Run:102\n\tsilos3.com/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78”}

Ports are forwarded, and according to localhost:28967

{
“Statuses”: null,
“Help”: “To access Storagenode services, please use DRPC protocol!”,
“AllHealthy”: true
}

All was working fine a few hours before.

Thank you,

Hester

2

Share Screenshot of Your node portal: http://127.0.0.1:14002

also, check one more thing: if you are using no-ip, you set up an auto IP update service of no-ip.
(maybe your internet provider changed your IP and the no-ip domain has not updated your IP)

3

Hi!

I found the problem, i had no group/host selected in DUC.

Node is connected again after i restarted docker container.

Thank you,

Hester

1 Like