since 3 days I try myself on StoreJ. I didn’t have any experience with the tokens beforehand, which put some obstacles in my way. Also that the default of the app data was on Program Data instead of AppData was a bit irritating. But I solved all problems.
Now everything should work, but the start hangs on the following error.
The first entry in the logs after startup looks like this:
ERROR contact:service ping satellite failed {
"Satellite ID": "..ID..", "attempts": 6,
"error": "ping satellite: failed to dial storage node (ID: ..ID..) at address adress.myfritz.net:28967: rpc: dial tcp ..MYIP..:28967: connect: no route to host",
"errorVerbose": "ping satellite: failed to dial storage node (ID: ..ID..) at address adress.myfritz.net:28967: rpc: dial tcp ..MYIP..: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:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.
(*Group).Go.func1:57"
}
The hostname it resolves is correct, because it resolves my IP external IP address correctly.
In addition, the port can also be called from outside with external tests, yet the connection is not established properly. Do you have any ideas where the possible causes could be?
I use MyFritz as DNS about Unitymedia Ipv4 available and a Win 10 as operating system.
Check your port forwarding rule on your router - it should forward 28967 TCP+UDP port to 28967 port and IP of your PC with storagenode. You should not specify the source IP, it must be either ANY or empty. The source network interface (if your router requires it) should be your ISP.
Have corrected the post. Had because it was my ESXI server the hostname ESXI deposited in the Fritzbox. But because I now Windows always boot for mining & Co. the Fritzbox has now taken the Windows hostname Desktop-ABC123 and I have not noticed.
For other users: Check the Port Forwarding correct (IP AND Hostname). Trust is good, control is better!
That i have done already before. But thx for the hint. I have do the step complete again.
Now i getting this message:
FATAL Unrecoverable error {
"error": "piecestore monitor: error verifying location and/or readability of storage directory: node ID in file (12V*****PNE) does not match running node's ID (12V*****P52)",
"errorVerbose": "piecestore monitor: error verifying location and/or readability of storage directory: node ID in file (12V*****P52) does not match running node's ID (12V*****P52)
\n\tstorj.io/storj/storagenode/monitor.
(*Service).Run.func1.1:131\n\tstorj.io/common/sync2.
(*Cycle).Run:92\n\tstorj.io/storj/storagenode/monitor.
(*Service).Run.func1:128\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
This is mean that you generated a new identity instead of signing the previous one.
If you want to lose node (12V*****PNE), then you should remove all data and perform the setup step again.
If it’s not intendent - then restore (12V*****PNE) from backup and sign it with a new authorization token, then try to run the node.