Node offline after move to different ubuntu pc

I moved the node and its identity to different ubuntu pc - PC2 (former had a different node on it but that node was moved back to it original pc - PC1 after recovering that pc from a crash.)
Now the node and idenity on PC3 is moved to pC2 gives these errors for every satellite:

2021-11-06T02:10:57.288Z WARN console:service unable to get Satellite URL {“Satellite ID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “error”: “console: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted”, “errorVerbose”: “console: trust: satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” is untrusted\n\*Pool).getInfo:238\n\*Pool).GetNodeURL:177\n\*Service).GetDashboardData:174\n\*StorageNode).StorageNode:45\n\tnet/http.HandlerFunc.ServeHTTP:2046\n\*Router).ServeHTTP:210\n\tnet/http.serverHandler.ServeHTTP:2878\n\tnet/http.(*conn).serve:1929”}
2021-11-06T02:12:48.353Z ERROR contact:service ping satellite failed {“Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “attempts”: 10, “error”: “ping satellite: check-in ratelimit: node rate limited by id”, “errorVerbose”: “ping satellite: check-in ratelimit: node rate limited by id\n\*Service).pingSatelliteOnce:138\n\*Service).pingSatellite:95\n\*Chore).updateCycles.func1:87\n\*Cycle).Run:92\n\*Cycle).Start.func1:71\n\*Group).Go.func1:57”}

The moved node on PC2 has the same name as the prior node that was on PC2 and which is now on PC1.

Here is the recap
PC1 ubuntnu crashes. Node and identity on PC1 is moved to PC2 - a new ubuntu build, and is running fine. PC1 is fixed (took 3 days). Node and identity on PC2 is then moved back to PC1 and is runnning fine. A different node and identity on PC3 is the moved to a new ubuntu build on PC2. Docker setup looks good:
1c4c58d8c2fe storjlabs/watchtower “/watchtower storage…” 12 minutes ago Up 12 minutes watchtower
7c774aae62fc storjlabs/storagenode:latest “/entrypoint” 19 minutes ago Up 19 minutes>14002/tcp,>28967/tcp, :::46010->28967/tcp storagenode

But the web dashboard says offline and the log show the errors listed above.

How to fix PC2 without loosing the node?

Any help is greatly appreciate.

EDIT: V1.41.2

This is Stefan satellite, and it was shutdown last year, so, yeah, it’s untrusted. You can ignore this warning.
The second one about rate limit is result of your node being offline and trying to check-in too often without fixing the reachability issue.

The offline usually happen when you mess up with port forwarding (I think that’s your case) or internal IP or external IP got changed.

Please, check the IP of the PC where this node is running and make sure that the port forwarding rule uses the same local IP as a destination and the same external port where you node is listening: Step 3. Setup Port Forwarding - Storj Docs

The next step would be your firewall - you need to allow the port from the left part of the -p option of your docker run command in the inbound firewall rules for TCP and UDP.
Then check your external address, it could change and you need either update your DDNS address or ADDRESS option in the docker run command if you prefer to use a public IP.

Make sure that the external port in the ADDRESS parameter matches external port in the port forwarding rule for this PC on your router.
The destination (local) port in the port forwarding rule must match the port from the left part of the -p option,

For example, if your external port is 28969, the left part of port mapping is 28968, and local IP of your PC is, then port forwarding rule could look like this:

Source External port Protocol Local port Destination
ISP 28969 TCP+UDP 28968

The docker run command will contain:

docker run ... \
  -p 28968:28967/tcp \
  -p 28968:28967/udp \
  -e ADDRESS=my.ddns.external.address:28969 \

Thank you for the detailed response. I used the wrong external IP address. Removed the container and reran the docker run command and now the dashboard shows online.

Much appreciated.

1 Like