Node just went offline after unecpected UIC misconfigured

Node Operators troubleshooting
, , ,
1

Node just went offline after an unexpected UIC misconfigured before it worked without problems for several months, no settings changed, all ports are open, DNS 1.1.1.1, tried restarting the container with the option --dns 1.1.1.1 and 8.8.8.8.

$docker logs storagenode
2024-12-03T09:43:48Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 11, "error": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 109.110.51.197:28967: connect: connection timed out", "errorVerbose": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 109.110.51.197:28967: connect: connection timed out\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:209\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:157\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}

How else can I try to solve the problem?

2

Check that this is still your external IP address, that the port is still forwarded to the correct lan device at the correct ip address, that the firewall or other security software on the gateway does not block these connections, and the same on the device that runs a node.

4 Likes
3

i also got this on one node.
maybe there is some issue.

4

Hello @nano,
Welcome back!

You need to check, that your external IP has not changed, also please check the local IP of your host with the node, if you didn’t configure a static local IP for it on your router and your router is unable to detect the IP change automatically, you need to update the local IP in the port-forwarding rule and make it static in the DHCP section to do not have this issue again.

5

I have a static ip and if i connect from a differen5 machine i got this response.

curl 104.xxx.xxx.xxx:5145
{
“Statuses”: null,
“Help”: “To access Storagenode services, please use DRPC protocol!”,
“AllHealthy”: false
}
So the connection should not be the issue. The Node worked for a long time and i didnt change a thing. So very strage.

6

It is always a DNS Problem. I changed the DNS on my Gateway, and boom. Worked Again.
The strage thing is, on my other machine was the same DNS without a problem.

1 Like