Node offline after (physically) moving

Node Operators troubleshooting
,
1

Hey all,

Node showing suspended (I hope not permanently) after a neighborhood move. Here’s the last few messages from the log. I could have changed IP incorrectly? I honestly don’t remember which one I used since I set it up since that was a while ago. It’s been up for a while but showing offline on the node page.

     2021-07-26T17:59:51.347Z	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 8, "error": "ping satellite: failed to dial storage node (ID: 12ZTnxxVhVwTdRD8RrDHUTxqpCp1aUHXpWttquJnEj9uA1GGMcA) at address canistorjthishere.ddns.net:28967: rpc: dial tcp 207.38.227.113:28967: connect: no route to host", "errorVerbose": "ping satellite: failed to dial storage node (ID: 12ZTnxxVhVwTdRD8RrDHUTxqpCp1aUHXpWttquJnEj9uA1GGMcA) at address canistorjthishere.ddns.net:28967: rpc: dial tcp 207.38.227.113:28967: connect: no route to host\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:141\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:152\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-07-26T18:00:20.486Z	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "attempts": 12, "error": "ping satellite: failed to dial storage node (ID: 12ZTnxxVhVwTdRD8RrDHUTxqpCp1aUHXpWttquJnEj9uA1GGMcA) at address canistorjthishere.ddns.net:28967: rpc: dial tcp 207.38.227.113:28967: connect: no route to host", "errorVerbose": "ping satellite: failed to dial storage node (ID: 12ZTnxxVhVwTdRD8RrDHUTxqpCp1aUHXpWttquJnEj9uA1GGMcA) at address canistorjthishere.ddns.net:28967: rpc: dial tcp 207.38.227.113:28967: connect: no route to host\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:141\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:152\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-07-26T18:01:32.499Z	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB", "attempts": 9, "error": "ping satellite: check-in ratelimit: node rate limited by id", "errorVerbose": "ping satellite: check-in ratelimit: node rate limited by id\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:138\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:152\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2021-07-26T18:01:59.767Z	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 9, "error": "ping satellite: check-in ratelimit: node rate limited by id", "errorVerbose": "ping satellite: check-in ratelimit: node rate limited by id\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:138\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:152\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2

Hi @aboveminimums ,
Thanks for letting us know. I’ve forwarded this to the team for some answers.

3

Hi @aboveminimums , please try out these steps! My Node is OFFLINE for 2 hours - #2 by BrightSilence

4

Suggests that your DDNS hostname either have a typo or you forgot to extend the DDNS subscription (you need to confirm it every month on free plan).
Also worth to check your port forwarding rule on your router - did you update the destination for 28967?

If it’s after migration to the other network - make sure that DDNS updater did not run on the old network and works only in the network with that node. Maybe better to configure DDNS updater on your router instead of DUC.

5

Hi alexey, I think this may be the problem. Been avoiding this for a few days because I’m scared to mess it up more…

When I try to find the IP using the linux command in the terminal it brings up a number of different IPs. Which one should I be putting on for port forwarding?

6

The one which bind to your ethernet adapter (eth0 for example), I could help to select, if you share the output of the command

ip address

However, this address should not be placed anywhere in the config.yaml, this is local address, unavailable from outside. It is needed only for port forwarding rule on your router (it should be a destination, where a source is “any” or “internet” or “ISP” but NOT an IP)