Second node startup error

[ACarneiro]

I’m really sorry to be posting yet again with a second node issue.

I’ve created a new identity, authorised it, moved all the stuff to the destination machine, adjusted all the port forwards on my docker command and getting an error on the dashboard (screenshot attached)

Upon checking the logs, I see this

2020-06-23T11:10:47.884Z ERROR nodestats:cache Get pricing-model/join date failed {“error”: “heldamount service error: node not found: 12QCDCHmaaKFbpk874tiqoD68Kqu9nWwBcitQiX9rnJnwuwAmng; heldamount service error: node not found: 12QCDCHmaaKFbpk874tiqoD68Kqu9nWwBcitQiX9rnJnwuwAmng; heldamount service error: node not found: 12QCDCHmaaKFbpk874tiqoD68Kqu9nWwBcitQiX9rnJnwuwAmng”, “errorVerbose”: “group:\n— heldamount service error: node not found: 12QCDCHmaaKFbpk874tiqoD68Kqu9nWwBcitQiX9rnJnwuwAmng\n\tstorj.io/storj/storagenode/heldamount.(*Service).GetAllPaystubs:132\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func1:78\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:233\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run:77\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func1:56\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57\n— heldamount service error: node not found: 12QCDCHmaaKFbpk874tiqoD68Kqu9nWwBcitQiX9rnJnwuwAmng\n\tstorj.io/storj/storagenode/heldamount.(*Service).GetAllPaystubs:132\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func1:78\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:233\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run:77\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func1:56\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57\n— heldamount service error: node not found: 12QCDCHmaaKFbpk874tiqoD68Kqu9nWwBcitQiX9rnJnwuwAmng\n\tstorj.io/storj/storagenode/heldamount.(*Service).GetAllPaystubs:132\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func1:78\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:233\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run:77\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func1:56\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}

Can anyone shed some light on where I cocked this up?

[odarriba]

That error usually means that your node is not reachable from the outside. Maybe you can check your port forwarding and the external address configuration of your node.

[ACarneiro]

Checked and triple checked. The outside ports are open and directing to the correct internal ports…

[odarriba]

Have you checked the points of this post? They are very useful for debugging connectivity issues.

My Node is OFFLINE for 2 hours

It should connect in seconds. There are a few things you should check. Start with checking the port. On https://www.yougetsignal.com/tools/open-ports/?port=28967 you can fill in the domain or IP you are using in the run command. Then check the port. If it’s closed, it could still be several things. Make sure the WAN IP you see in your router settings matches the IP shown on the above page. Make sure your port forward is set up correctly. That means no filter on incoming IPs, forwarding to th…

As I can see on other related topics, the heldamount error is a common one when the node is shown as OFFLINE, which is the real problem.

[ACarneiro]

Ah, hang on. I think I’m missing a couple of files in the identity folder…

[ACarneiro]

I am, as suspected, an idiot.
Somehow didn’t copy the signed certs after authorising the identity. All up and running now, sorry to have wasted all of your time