Docs about Port-forwarding on TrueNAS

Node Operators getting started
,
21

So TrueNAS GUI and video guide have the default port as 20988; however, when I use that port I get an error that I need to use port 28967 for QUIC. However, when I use that port, the error doesn’t go away. In each case, I port forward the port in question (using same port for both external/public and internal/private).

I may have mistyped “28966”; I cannot find where I got that port now, with all the different sites I’m looking through.

Also, in each case I tested to be sure the port was open, and it was.

22

Ok, as it is running as a container the QUIC tooltip has no effect, as it is using 28967 internally anyway.

While installing the app the “Node Port for Storj” in the networking section is the point where you have to tell truenas which port you actually want to use externally for it to reroute.
For Example if you use 20988 ( I dont’t know why they chose this one)

outside world => 20988 => router => 20988=> node machine => 20988 [“Node Port for Storj”] => docker container => 28967 storj app inside container and which is reported on tooltip

You may also just use 28967 if it is not used elsewehere.
And how did you test the port is open?

EDIT: QUIC was working, now not - a few booboo's on the way - #4 by aardvarkl

1 Like
24

He used portcheck.co to test the port. And he set everything to port 28967 (external/internal ports for forwarding & node port in UI).

He’s still getting the QUIC error. But thinking he needed to get a new identity token, now he’s getting numerous of the following errors for different nodes in the log:

2023-07-29 16:03:54.363554+00:002023-07-29T16:03:54Z ERROR contact:service ping satellite failed {“process”: “storagenode”, “Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “attempts”: 8, “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:203\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:157\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}

He also tried the TrueCharts app, but it doesn’t have anywhere to provide either the auth token, so he’s back to TrueNAS Charts app.

25

Also, he is cannot post for 13 hours owing to community rules, thus my reply

26

in this log I do not see multiple nodes but one node that is not reachable
If there are multiple running now he should try to clean the unused ones.

 ERROR contact:service ping satellite failed

there is another issue apart from the quick error, could be the same though
Did he set the WAN IP / DDNS?
Outbound traffic filtered?

27

I only posted one of the many identical errors, each with a different node address. Now, after trying various things, the logs are basically all errors of various sorts. Worth posting? I could have him send me.

He set up his WAN IP with DDNS, yes. And TrueNAS is, by default, set to allow all outgoing traffic.

Is there a official support he could contact to work one on one to solve this? He’s not sure which to even turn to next. I think he would pay someone at this point, lol

28

Are these really multiple node IDs or just the different satellite IDs or to which addresses you are referring to?
Since I don’t know how this could look like you can post a bit more, that’s what the forum is for.
Or if it has been messed up too much just start from scratch. :innocent:

There is official support here https://support.storj.io/hc/en-us but I neither know nor think they provide one on one node setup support. this is mostly handled here in the forum , also from the official side.

I think if he is stuck himself the best chance is the forum here or that of truenas.

29

OK, thanks.

Here is a good chunk of the storj log, beginning from errors (it seems to largely repeat after this):
2023-07-30T01:39:39.132352423Z
2023-07-30T01:39:39.132407957Z 2023-07-30 01:39:39 (78.1 MB/s) - ‘/tmp/storagenode.zip’ saved [17483827/17483827]
2023-07-30T01:39:39.132415140Z
2023-07-30T01:39:39.377276711Z 2023-07-30 01:39:39,377 INFO RPC interface ‘supervisor’ initialized
2023-07-30T01:39:39.377323789Z 2023-07-30 01:39:39,377 INFO supervisord started with pid 1
2023-07-30T01:39:40.378845285Z 2023-07-30 01:39:40,378 INFO spawned: ‘processes-exit-eventlistener’ with pid 66
2023-07-30T01:39:40.379529806Z 2023-07-30 01:39:40,379 INFO spawned: ‘storagenode’ with pid 67
2023-07-30T01:39:40.380150847Z 2023-07-30 01:39:40,380 INFO spawned: ‘storagenode-updater’ with pid 68
2023-07-30T01:39:40.384324674Z 2023-07-30T01:39:40Z INFO Configuration loaded {“Process”: “storagenode-updater”, “Location”: “/app/config/config.yaml”}
2023-07-30T01:39:40.384334663Z 2023-07-30T01:39:40Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “console.address”}
2023-07-30T01:39:40.384339311Z 2023-07-30T01:39:40Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet-features”}
2023-07-30T01:39:40.384358958Z 2023-07-30T01:39:40Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “contact.external-address”}
2023-07-30T01:39:40.384362785Z 2023-07-30T01:39:40Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “healthcheck.details”}
2023-07-30T01:39:40.384375790Z 2023-07-30T01:39:40Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.private-address”}
2023-07-30T01:39:40.384379547Z 2023-07-30T01:39:40Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet”}
2023-07-30T01:39:40.384395426Z 2023-07-30T01:39:40Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-bandwidth”}
2023-07-30T01:39:40.384399083Z 2023-07-30T01:39:40Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-disk-space”}
2023-07-30T01:39:40.384402840Z 2023-07-30T01:39:40Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.address”}
2023-07-30T01:39:40.384414322Z 2023-07-30T01:39:40Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.email”}
2023-07-30T01:39:40.384418279Z 2023-07-30T01:39:40Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “healthcheck.enabled”}
2023-07-30T01:39:40.384431023Z 2023-07-30T01:39:40Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.level”}
2023-07-30T01:39:40.384434880Z 2023-07-30T01:39:40Z INFO Anonymized tracing enabled {“Process”: “storagenode-updater”}
2023-07-30T01:39:40.384599929Z 2023-07-30T01:39:40Z INFO Running on version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.84.1”}
2023-07-30T01:39:40.384807096Z 2023-07-30T01:39:40Z INFO Downloading versions. {“Process”: “storagenode-updater”, “Server Address”: “https://version.storj.io”}
2023-07-30T01:39:40.399641782Z 2023-07-30T01:39:40Z INFO Configuration loaded {“process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2023-07-30T01:39:40.399773939Z 2023-07-30T01:39:40Z INFO Anonymized tracing enabled {“process”: “storagenode”}
2023-07-30T01:39:40.400462326Z 2023-07-30T01:39:40Z INFO Operator email {“process”: “storagenode”, “Address”: “XXXX”}
2023-07-30T01:39:40.400530243Z 2023-07-30T01:39:40Z INFO Operator wallet {“process”: “storagenode”, “Address”: “XXXX”}
2023-07-30T01:39:40.486206105Z 2023-07-30T01:39:40Z INFO server kernel support for server-side tcp fast open remains disabled. {“process”: “storagenode”}
2023-07-30T01:39:40.486289942Z 2023-07-30T01:39:40Z INFO server enable with: sysctl -w net.ipv4.tcp_fastopen=3 {“process”: “storagenode”}
2023-07-30T01:39:40.540147132Z 2023-07-30T01:39:40Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode”, “Version”: “v1.84.1”}
2023-07-30T01:39:40.540161559Z 2023-07-30T01:39:40Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode”}
2023-07-30T01:39:40.542689307Z 2023-07-30T01:39:40Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.84.1”}
2023-07-30T01:39:40.542699075Z 2023-07-30T01:39:40Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”}
2023-07-30T01:39:40.662178830Z 2023-07-30T01:39:40Z INFO Telemetry enabled {“process”: “storagenode”, “instance ID”: “12jQvhZ1fGvLei12oWHwkHjye2F7odJBeEAHuSzjv8fSQpTVZvE”}
2023-07-30T01:39:40.662219607Z 2023-07-30T01:39:40Z INFO Event collection enabled {“process”: “storagenode”, “instance ID”: “12jQvhZ1fGvLei12oWHwkHjye2F7odJBeEAHuSzjv8fSQpTVZvE”}
2023-07-30T01:39:40.674295773Z 2023-07-30T01:39:40Z INFO db.migration Database Version {“process”: “storagenode”, “version”: 54}
2023-07-30T01:39:41.067999305Z 2023-07-30T01:39:41Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock. {“process”: “storagenode”}
2023-07-30T01:39:41.776910347Z 2023-07-30T01:39:41Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock. {“process”: “storagenode”}
2023-07-30T01:39:41.777022838Z 2023-07-30 01:39:41,776 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-30T01:39:41.777103769Z 2023-07-30 01:39:41,777 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-30T01:39:41.777145758Z 2023-07-30 01:39:41,777 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-30T01:39:41.777260582Z 2023-07-30T01:39:41Z INFO bandwidth Performing bandwidth usage rollups {“process”: “storagenode”}
2023-07-30T01:39:41.777266463Z 2023-07-30T01:39:41Z INFO trust Scheduling next refresh {“process”: “storagenode”, “after”: “4h50m9.83735722s”}
2023-07-30T01:39:41.777283355Z 2023-07-30T01:39:41Z INFO Node 12jQvhZ1fGvLei12oWHwkHjye2F7odJBeEAHuSzjv8fSQpTVZvE started {“process”: “storagenode”}
2023-07-30T01:39:41.777287212Z 2023-07-30T01:39:41Z INFO Public server started on [::]:28967 {“process”: “storagenode”}
2023-07-30T01:39:41.777290378Z 2023-07-30T01:39:41Z INFO Private server started on 127.0.0.1:7778 {“process”: “storagenode”}
2023-07-30T01:39:41.777302471Z 2023-07-30T01:39:41Z INFO pieces:trash emptying trash started {“process”: “storagenode”, “Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”}
2023-07-30T01:39:41.777306198Z 2023-07-30T01:39:41Z INFO failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See UDP Receive Buffer Size · quic-go/quic-go Wiki · GitHub for details. {“process”: “storagenode”}
2023-07-30T01:39:41.777332206Z 2023-07-30T01:39:41Z INFO pieces:trash emptying trash started {“process”: “storagenode”, “Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”}
2023-07-30T01:39:41.777343588Z 2023-07-30T01:39:41Z INFO pieces:trash emptying trash started {“process”: “storagenode”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”}
2023-07-30T01:39:41.777361431Z 2023-07-30T01:39:41Z INFO pieces:trash emptying trash started {“process”: “storagenode”, “Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”}
2023-07-30T01:39:41.777386157Z 2023-07-30T01:39:41Z INFO pieces:trash emptying trash started {“process”: “storagenode”, “Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”}
2023-07-30T01:39:41.777407207Z 2023-07-30T01:39:41Z INFO pieces:trash emptying trash started {“process”: “storagenode”, “Satellite ID”: “12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo”}
2023-07-30T01:39:41.984051257Z 2023-07-30T01:39:41Z ERROR contact:service ping satellite failed {“process”: “storagenode”, “Satellite ID”: “12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo”, “attempts”: 1, “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:209\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:157\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
2023-07-30T01:39:42.077882633Z 2023-07-30T01:39:42Z ERROR contact:service ping satellite failed {“process”: “storagenode”, “Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “attempts”: 1, “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:209\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:157\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
2023-07-30T01:39:42.236691526Z 2023-07-30T01:39:42Z ERROR contact:service ping satellite failed {“process”: “storagenode”, “Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “attempts”: 1, “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:209\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:157\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
2023-07-30T01:39:42.299940572Z 2023-07-30T01:39:42Z ERROR contact:service ping satellite failed {“process”: “storagenode”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “attempts”: 1, “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:209\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:157\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
2023-07-30T01:39:42.484208463Z 2023-07-30T01:39:42Z ERROR contact:service ping satellite failed {“process”: “storagenode”, “Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”, “attempts”: 1, “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:209\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:157\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
2023-07-30T01:39:42.835737465Z 2023-07-30T01:39:42Z ERROR contact:service ping satellite failed {“process”: “storagenode”, “Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “attempts”: 1, “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:209\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:157\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
2023-07-30T01:39:43.179701729Z 2023-07-30T01:39:43Z ERROR contact:service ping satellite failed {“process”: “storagenode”, “Satellite ID”:

Here is a chunk of the setup log:
2023-07-30T01:39:24.469245241Z
2023-07-30T01:39:24.469280307Z 2023-07-30 01:39:24 (46.6 MB/s) - ‘/tmp/storagenode.zip’ saved [17483827/17483827]
2023-07-30T01:39:24.469285166Z
2023-07-30T01:39:24.692970660Z 2023-07-30 01:39:24,692 INFO RPC interface ‘supervisor’ initialized
2023-07-30T01:39:24.693028638Z 2023-07-30 01:39:24,692 INFO supervisord started with pid 6
2023-07-30T01:39:25.695095444Z 2023-07-30 01:39:25,694 INFO spawned: ‘processes-exit-eventlistener’ with pid 66
2023-07-30T01:39:25.695667404Z 2023-07-30 01:39:25,695 INFO spawned: ‘storagenode’ with pid 67
2023-07-30T01:39:25.696160056Z 2023-07-30 01:39:25,696 INFO spawned: ‘storagenode-updater’ with pid 68
2023-07-30T01:39:25.701082792Z 2023-07-30T01:39:25Z INFO Configuration loaded {“Process”: “storagenode-updater”, “Location”: “/app/config/config.yaml”}
2023-07-30T01:39:25.701098862Z 2023-07-30T01:39:25Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “console.address”}
2023-07-30T01:39:25.701104263Z 2023-07-30T01:39:25Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-disk-space”}
2023-07-30T01:39:25.701126164Z 2023-07-30T01:39:25Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.private-address”}
2023-07-30T01:39:25.701130061Z 2023-07-30T01:39:25Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.address”}
2023-07-30T01:39:25.701140991Z 2023-07-30T01:39:25Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.email”}
2023-07-30T01:39:25.701145149Z 2023-07-30T01:39:25Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “healthcheck.enabled”}
2023-07-30T01:39:25.701155689Z 2023-07-30T01:39:25Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-bandwidth”}
2023-07-30T01:39:25.701159316Z 2023-07-30T01:39:25Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “contact.external-address”}
2023-07-30T01:39:25.701162842Z 2023-07-30T01:39:25Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “healthcheck.details”}
2023-07-30T01:39:25.701172901Z 2023-07-30T01:39:25Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet”}
2023-07-30T01:39:25.701176598Z 2023-07-30T01:39:25Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet-features”}
2023-07-30T01:39:25.701186997Z 2023-07-30T01:39:25Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.output”}
2023-07-30T01:39:25.701190804Z 2023-07-30T01:39:25Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.stack”}
2023-07-30T01:39:25.701200743Z 2023-07-30T01:39:25Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.development”}
2023-07-30T01:39:25.701204460Z 2023-07-30T01:39:25Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.encoding”}
2023-07-30T01:39:25.701208487Z 2023-07-30T01:39:25Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.level”}
2023-07-30T01:39:25.701219809Z 2023-07-30T01:39:25Z INFO Anonymized tracing enabled {“Process”: “storagenode-updater”}
2023-07-30T01:39:25.701287545Z 2023-07-30T01:39:25Z INFO Running on version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.84.1”}
2023-07-30T01:39:25.701420684Z 2023-07-30T01:39:25Z INFO Downloading versions. {“Process”: “storagenode-updater”, “Server Address”: “https://version.storj.io”}
2023-07-30T01:39:25.717195689Z 2023-07-30T01:39:25Z INFO Configuration loaded {“process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2023-07-30T01:39:25.717338386Z 2023-07-30T01:39:25Z INFO Anonymized tracing enabled {“process”: “storagenode”}
2023-07-30T01:39:25.718070034Z 2023-07-30T01:39:25Z WARN Operator email address isn’t specified. {“process”: “storagenode”}
2023-07-30T01:39:25.718078460Z 2023-07-30T01:39:25Z ERROR Invalid configuration. {“process”: “storagenode”, “error”: “operator wallet address isn’t specified”}
2023-07-30T01:39:25.718094009Z Error: operator wallet address isn’t specified
2023-07-30T01:39:25.718638247Z 2023-07-30 01:39:25,718 INFO exited: storagenode (exit status 1; not expected)
2023-07-30T01:39:25.843823293Z 2023-07-30T01:39:25Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode”, “Version”: “v1.84.1”}
2023-07-30T01:39:25.843862357Z 2023-07-30T01:39:25Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode”}
2023-07-30T01:39:25.846379124Z 2023-07-30T01:39:25Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.84.1”}
2023-07-30T01:39:25.846397909Z 2023-07-30T01:39:25Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”}
2023-07-30T01:39:26.848027287Z 2023-07-30 01:39:26,847 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-30T01:39:26.849084555Z 2023-07-30 01:39:26,848 INFO spawned: ‘storagenode’ with pid 104
2023-07-30T01:39:26.849214548Z 2023-07-30 01:39:26,849 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-30T01:39:26.867283923Z 2023-07-30T01:39:26Z INFO Configuration loaded {“process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2023-07-30T01:39:26.867331402Z 2023-07-30T01:39:26Z INFO Anonymized tracing enabled {“process”: “storagenode”}

Hard to know how much to post, so sorry about all this!

Eumaios send his thanks!

30

You may want to remove his personal info like email and wallet address.

Meanwhile I’ll have a look

edit:
ok so the first part looks good except that the node is not reachable.
the second part is missing some data like the wallet address. Is this the same node only earlier in time, as seen in the timestamps?

1 Like
31

The two logs were downloaded at about the same time, one right after the other.

He is certain he provided his wallet address. Is it possible One Key wallet isn’t compatible? It accepts ERC20 token.

32

Yes it’s only a couple of seconds, maybe part of the setup process. The first part you posted, which I assume was the later has a valid wallet address. If that’s all, at least the node itself is fine.

Now if the port is reported open there is something running. What happens if he or you put the node ip:port in a browser? Maybe the port is already in use by something else?

33

No, the port isn’t being used by anything else. It’s closed when Storj isn’t running, and open when it is (and ‘he’ checked all open ports).

34

If it’s only open when storj is running you should get a response it you paste the “ddns:port” which storj is running at in the browser

35

I get this:

{
“Statuses”: null,
“Help”: “To access Storagenode services, please use DRPC protocol!”,
“AllHealthy”: false
}

36

This is a good sign. That means the node is accessible from external.

… I’m sorry I missed the very long line after ERROR contact:service ping satellite failed
The issue now is that the Identity is not signed. (Auth token)

37

Yea. Not sure why that is happening. There is nothing in the TrueNAS guides about this “signing” process.

38

It should be done automatically if i read this correct

  1. Enter the authentication token copied from Storj in Configure Auth token for Storj Node. Enter the email address associated with the token in Configure Email for Storj.
39

Agreed. And yet, here we are…

40

does the auth token include the email?! I recall getting the token and it started with the email address. I deleted that when I entered it in TrueNAS

41

Yes the email is part of it and you need to provide the whole key.