New to Storj and trying to get it up running on TrueNas Scale. I followed the directions found here: Setting Up a Storj Node | and their youtube video
Initially, they seem a bit incomplete. For example it didn’t mention I needed to allow port 7777 outbound. But after a bit of working around I was able to get most communication working.
In the instructions it said to forward 20988 which didn’t result in a working node so I changed the configuration both on TrueNAS and on the firewall to what you have on the website here “28967” and I was able to validate that connectivity can be established via Open Port Check Tool - Test Port Forwarding on Your Router.
What I am left with is the following error message in logs:
RROR contact:service ping satellite failed {“Process”: “storagenode”, “Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”, “attempts”: 11, “error”: “ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: not signed by any CA in the whitelist: CA cert”, “errorVerbose”: “ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: not signed by any CA in the whitelist: CA cert\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:149\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:102\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:160\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
and in the web interface I am shown that the node is offline and that QUIC is misconfigured. Not sure how this can be since I am able to validate the port connectivity. I’ve seen a couple of posts about the identity being wrong but I’m not sure what else I can do to correct it?
Is this a new TrueNAS Scale setup or have you had it for a while? I had some certificate errors when I first installed Scale because it was hosted in a VM and was on a 172 subnet.
You might try switching ports as well. There may be some reason they suggested using the +1 port number in the instructions. Possibly the other port is occupied.
Correct - this is a brand new TrueNAS scale setup. Everything else is running. I’ve tried using their suggested port as well as the standard QUIC port 28967 but neither is working. This is hosted on a bare-metal box in a 192.168.x.x subnet.
You might want to try the TrueNAS forum for additional help here as I am not certain if there are any internal routing or firewall configurations with TrueNAS that you would have to adjust.
This error usually means your identity isn’t signed. Can you check the identity location? There should be 6 files. If only 4 files then you need to go through the steps again to sign the identity.
I’ve only ever had 4 files in there. I’ve actually blown the entire thing away several times now and started over for your exact reasoning its always the same result.
Yup! I had found that same article! I wish the poster stated what “tinkering” he did. It would probably have helped a ton. I’m trying a totally fresh deploy (again) to triple-check I didn’t screw something, and crossing my fingers that I get lucky and it works.
Your deploy is fine. The only thing you should do is authenticate the identity on your computer and copy the 6 files to the identity dataset. This guy posted a list of tasks - Need help setting up multiple nodes | TrueNAS Community - it’s the top 3 where your problem lies.
By the way, when you setup a node (and generate an identity), you need to obtain a new authorization token every attempt, because the old one become used and it’s a one-time usage token.
Hey Alexey! Thanks for the welcome and the information. How do you create a new authorization token? Whenever I go Sign up and host a Node on Storj it gives me the same token.
I think it gives you the one until you use it, and then it would give you a new one. Since your identity hasn’t been signed, it hasn’t been registered as used. I am surprised the tool didn’t do the identity part for you in the setup. I wonder if there was an error in TrueNAS Scale that prevented it from working.
Hey all!! Solved and Update time! The solution was a combination of things missing from the docs and steps that need to be taken.
@Stob you’re advice should be followed prior to trying to even install the app. Create the identity on the outside of truenas and move it there via NFS or some other mechanism of your choosing. If you try and “correct” the issue by doing it after deploying the “config” folder causes more issues/headache with mismatching node ID’s and things.
Ports that need to be open in addition to what TN says: 8888 and 7777. 8888 is used in the identity signing portion. Im thinking this can be ignored/blocked if you do the signing outside of truenas. 7777 looks to be necessary for communication between satellites.
For some reason TrueNAS signing of the identity I never got to work but the app always started like it was normal. Im thinking there is additional filesystem-level permissions errors that prevented the writing of the signed certificates. Might do some more testing and propose addendums to the TrueNAS docs later. Thank you all for the prompt responses and troubleshooting!
Unlikely. The customers contact your node directly, not via the satellite.
The satellite is only address book, audit, repair and payment processor. All data is transferred directly between your node and the customer.
