Multinode dashboard unstable

Node Operators troubleshooting
,
1

Hello,

This version looks unstable Release v1.130.8 · storj/storj · GitHub linux amd, i update somtimes (and hope for better mobile support). Never got problem before this.

Up for 1 day, then this log, down until multinode restart.

2025-07-04T16:18:16+02:00       INFO    Configuration loaded    {"Location": "/multinode/config.yaml"}
2025-07-04T16:18:16+02:00       INFO    Anonymized tracing enabled
2025-07-04T16:18:16+02:00       INFO    db      Database Version        {"version": 0}
2025-07-05T07:32:46+02:00       ERROR   nodes:service   Could not fetch the version of the node:        {"error": "rpc: tcp connector failed: rpc: dial tcp: lookup storj-6.wtf.com: operation was canceled", "errorVerbose": "rpc: tcp connector failed: rpc: dial tcp: lookup storj-6.wtf.com: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190"}
2025-07-05T17:51:20+02:00       ERROR   bandwidth:service       Failed to fetch the monthly bandwidth summary of the node:      {"error": "bandwidth: rpc: tcp connector failed: rpc: dial tcp: lookup storj-1.wtf.com: operation was canceled", "errorVerbose": "bandwidth: rpc: tcp connector failed: rpc: dial tcp: lookup storj-1.wtf.com: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190"}
2025-07-05T17:51:20+02:00       ERROR   bandwidth:service       Failed to fetch the monthly bandwidth summary of the node:      {"error": "bandwidth: rpc: tcp connector failed: rpc: dial tcp: lookup storj-2.wtf.com: operation was canceled", "errorVerbose": "bandwidth: rpc: tcp connector failed: rpc: dial tcp: lookup storj-2.wtf.com: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190"}
2025-07-05T17:51:20+02:00       ERROR   nodes:service   Could not fetch the version of the node:        {"error": "rpc: tcp connector failed: rpc: dial tcp: lookup storj-6.wtf.com: operation was canceled", "errorVerbose": "rpc: tcp connector failed: rpc: dial tcp: lookup storj-6.wtf.com: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190"}
2025-07-05T17:51:20+02:00       ERROR   bandwidth:service       Failed to fetch the monthly bandwidth summary of the node:      {"error": "bandwidth: rpc: tcp connector failed: rpc: dial tcp: lookup storj-3.wtf.com: operation was canceled", "errorVerbose": "bandwidth: rpc: tcp connector failed: rpc: dial tcp: lookup storj-3.wtf.com: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190"}
2025-07-05T17:51:20+02:00       ERROR   bandwidth:service       Failed to fetch the monthly bandwidth summary of the node:      {"error": "bandwidth: rpc: tcp connector failed: rpc: dial tcp: lookup storj-4.wtf.com: operation was canceled", "errorVerbose": "bandwidth: rpc: tcp connector failed: rpc: dial tcp: lookup storj-4.wtf.com: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190"}
2025-07-05T17:51:20+02:00       ERROR   bandwidth:service       Failed to fetch the monthly bandwidth summary of the node:      {"error": "bandwidth: rpc: tcp connector failed: rpc: dial tcp: lookup storj-5.wtf.com: operation was canceled", "errorVerbose": "bandwidth: rpc: tcp connector failed: rpc: dial tcp: lookup storj-5.wtf.com: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190"}
2025-07-05T17:51:20+02:00       ERROR   bandwidth:service       Failed to fetch the monthly bandwidth summary of the node:      {"error": "bandwidth: rpc: tcp connector failed: rpc: dial tcp: lookup storj-6.wtf.com: operation was canceled", "errorVerbose": "bandwidth: rpc: tcp connector failed: rpc: dial tcp: lookup storj-6.wtf.com: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190"}
2

Hello @Oulalahakabu,
Welcome back!

Your nodes have a DNS issue, they cannot resolve the own domain.

1 Like
3

I changed the domain name in logs, it’s reachable from my network, sorry :slight_smile:

4

If the error is the same, like

then you still have this DNS issue. It must be resolvable not only internally, but also externally.

1 Like
5

I mean it is, i just avoid sharing my domain publicly so as not to annoy my ISP! :wink:

6

Multinode dashboard works great. I think there wasn’t even a code change. So the issue must be on your end.

3 Likes