It seems to be up now. I couldn’t access web ui earlier.
2 Likes
Yep, node is back online. All good now.
2 Likes
I’m trying to deploy test node, but I’ve some problems. I followed (I believe) steps here, this is what I see in my log:
2025-05-05 10:17:10,324 INFO Set uid to user 0 succeeded
2025-05-05 10:17:10,326 INFO RPC interface 'supervisor' initialized
2025-05-05 10:17:10,326 INFO supervisord started with pid 1
2025-05-05 10:17:11,329 INFO spawned: 'processes-exit-eventlistener' with pid 41
2025-05-05 10:17:11,331 INFO spawned: 'storagenode' with pid 42
2025-05-05 10:17:11,333 INFO spawned: 'storagenode-updater' with pid 43
2025-05-05T10:17:11Z INFO Configuration loaded {"Process": "storagenode-updater", "Location": "/app/config/config.yaml"}
2025-05-05T10:17:11Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.wallet"}
2025-05-05T10:17:11Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "healthcheck.enabled"}
2025-05-05T10:17:11Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "healthcheck.details"}
2025-05-05T10:17:11Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.address"}
2025-05-05T10:17:11Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.use-peer-ca-whitelist"}
2025-05-05T10:17:11Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.private-address"}
2025-05-05T10:17:11Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage2.trust.sources"}
2025-05-05T10:17:11Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.email"}
2025-05-05T10:17:11Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage.allocated-disk-space"}
2025-05-05T10:17:11Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "contact.external-address"}
2025-05-05T10:17:11Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "console.address"}
2025-05-05T10:17:11Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.wallet-features"}
2025-05-05T10:17:11Z INFO Anonymized tracing enabled {"Process": "storagenode-updater"}
2025-05-05T10:17:11Z INFO Running on version {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.126.2"}
2025-05-05T10:17:11Z INFO Downloading versions. {"Process": "storagenode-updater", "Server Address": "https://version.storj.io"}
2025-05-05T10:17:11Z INFO Configuration loaded {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2025-05-05T10:17:11Z INFO Anonymized tracing enabled {"Process": "storagenode"}
2025-05-05T10:17:11Z INFO Operator email {"Process": "storagenode", "Address": "anonymized@gmail.com"}
2025-05-05T10:17:11Z INFO Operator wallet {"Process": "storagenode", "Address": "0xanonymized"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "info"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "bandwidth"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "orders"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "piece_expiration"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "pieceinfo"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "piece_spaced_used"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "reputation"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "storage_usage"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "used_serial"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "satellites"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "notifications"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "heldamount"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "pricing"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "secret"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "garbage_collection_filewalker_progress"}
2025-05-05T10:17:11Z INFO db database does not exist {"Process": "storagenode", "database": "used_space_per_prefix"}
2025-05-05T10:17:11Z INFO server kernel support for server-side tcp fast open remains disabled. {"Process": "storagenode"}
2025-05-05T10:17:11Z INFO server enable with: sysctl -w net.ipv4.tcp_fastopen=3 {"Process": "storagenode"}
2025-05-05T10:17:11Z INFO Current binary version {"Process": "storagenode-updater", "Service": "storagenode", "Version": "v1.126.2"}
2025-05-05T10:17:11Z INFO Version is up to date {"Process": "storagenode-updater", "Service": "storagenode"}
2025-05-05T10:17:11Z INFO Current binary version {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.126.2"}
2025-05-05T10:17:11Z INFO Version is up to date {"Process": "storagenode-updater", "Service": "storagenode-updater"}
2025-05-05T10:17:11Z INFO Telemetry enabled {"Process": "storagenode", "instance ID": "1btpgAAB9roro8YQw4Td7LGQNc7o1rgtbX9x282M65KeXuGN5S"}
2025-05-05T10:17:11Z INFO Event collection enabled {"Process": "storagenode", "instance ID": "1btpgAAB9roro8YQw4Td7LGQNc7o1rgtbX9x282M65KeXuGN5S"}
2025-05-05 10:17:12,884 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-05-05 10:17:12,884 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-05-05 10:17:12,884 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-05-05T10:17:15Z INFO db.migration Database Created {"Process": "storagenode", "version": 62}
2025-05-05T10:17:15Z INFO preflight:localtime start checking local system clock with trusted satellites' system clock. {"Process": "storagenode"}
2025-05-05T10:17:15Z INFO preflight:localtime local system clock is in sync with trusted satellites' system clock. {"Process": "storagenode"}
2025-05-05T10:17:15Z INFO collector expired pieces collection started {"Process": "storagenode"}
2025-05-05T10:17:15Z INFO Node 1btpgAAB9roro8YQw4Td7LGQNc7o1rgtbX9x282M65KeXuGN5S started {"Process": "storagenode"}
2025-05-05T10:17:15Z INFO Public server started on [::]:28967 {"Process": "storagenode"}
2025-05-05T10:17:15Z INFO Private server started on 127.0.0.1:7778 {"Process": "storagenode"}
2025-05-05T10:17:15Z INFO failed to sufficiently increase send buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details. {"Process": "storagenode"}
2025-05-05T10:17:15Z INFO collector expired pieces collection completed {"Process": "storagenode", "count": 0}
2025-05-05T10:17:15Z INFO trust Scheduling next refresh {"Process": "storagenode", "after": "6h1m50.285821844s"}
2025-05-05T10:17:15Z INFO bandwidth Persisting bandwidth usage cache to db {"Process": "storagenode"}
2025-05-05T10:17:15Z INFO pieces:trash emptying trash started {"Process": "storagenode", "Satellite ID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU"}
2025-05-05T10:17:15Z INFO lazyfilewalker.trash-cleanup-filewalker starting subprocess {"Process": "storagenode", "satelliteID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU"}
2025-05-05T10:17:15Z INFO piecemigrate:chore all enqueued for migration; will sleep before next pooling {"Process": "storagenode", "active": {}, "interval": "10m0s"}
2025-05-05T10:17:15Z INFO lazyfilewalker.trash-cleanup-filewalker subprocess started {"Process": "storagenode", "satelliteID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU"}
2025-05-05T10:17:15Z INFO lazyfilewalker.trash-cleanup-filewalker.subprocess trash-filewalker started {"Process": "storagenode", "satelliteID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU", "dateBefore": "2025-04-28T10:17:15Z", "Process": "storagenode"}
2025-05-05T10:17:15Z INFO lazyfilewalker.trash-cleanup-filewalker.subprocess Database started {"Process": "storagenode", "satelliteID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU", "Process": "storagenode"}
05T10:17:15Z INFO lazyfilewalker.trash-cleanup-filewalker.subprocess trash-filewalker completed {"Process": "storagenode", "satelliteID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU", "Process": "storagenode", "bytesDeleted": 0, "numKeysDeleted": 0}
2025-05-05T10:17:15Z INFO lazyfilewalker.trash-cleanup-filewalker subprocess finished successfully {"Process": "storagenode", "satelliteID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU"}
2025-05-05T10:17:15Z INFO pieces:trash emptying trash finished {"Process": "storagenode", "Satellite ID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU", "elapsed": "62.108673ms"}
2025-05-05T10:17:17Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU", "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: tlsopts: peer ID did not match requested ID", "errorVerbose": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:216\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2025-05-05T10:17:19Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU", "attempts": 2, "error": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID", "errorVerbose": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:216\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2025-05-05T10:17:22Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU", "attempts": 3, "error": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID", "errorVerbose": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:216\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2025-05-05T10:17:26Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU", "attempts": 4, "error": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID", "errorVerbose": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:216\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2025-05-05T10:17:35Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU", "attempts": 5, "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:210\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2025-05-05T10:17:51Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU", "attempts": 6, "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:210\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2025-05-05T10:18:24Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU", "attempts": 7, "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:210\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2025-05-05T10:19:28Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU", "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:210\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2025-05-05T10:19:36Z ERROR nodestats:cache Get disk space usage query failed {"Process": "storagenode", "error": "nodestats: EOF", "errorVerbose": "nodestats: EOF\n\tstorj.io/storj/storagenode/nodestats.(*Service).GetDailyStorageUsage:73\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheSpaceUsage.func1:178\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:268\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheSpaceUsage:177\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func2:120\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2025-05-05T10:19:37Z ERROR nodestats:cache payouts err {"Process": "storagenode", "satellite": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU"}
05T10:19:37Z ERROR nodestats:cache Get held amount query failed {"Process": "storagenode", "error": "payouts service: node not found: 1btpgAAB9roro8YQw4Td7LGQNc7o1rgtbX9x282M65KeXuGN5S", "errorVerbose": "payouts service: node not found: 1btpgAAB9roro8YQw4Td7LGQNc7o1rgtbX9x282M65KeXuGN5S\n\tstorj.io/storj/storagenode/payouts.(*Endpoint).GetPaystub:73\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheHeldAmount.func1:211\n\tstorj.io/storj/storagenode/nodestats.(*Cache).satelliteLoop:268\n\tstorj.io/storj/storagenode/nodestats.(*Cache).CacheHeldAmount:203\n\tstorj.io/storj/storagenode/nodestats.(*Cache).Run.func2:125\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2025-05-05T10:21:01Z ERROR reputation:chore reputation chore failed {"Process": "storagenode", "error": "reputation: EOF", "errorVerbose": "reputation: EOF\n\tstorj.io/storj/storagenode/reputation.(*Service).GetStats:101\n\tstorj.io/storj/storagenode/reputation.(*Chore).GetAndCacheStats:93\n\tstorj.io/storj/storagenode/reputation.(*Chore).RunOnce:81\n\tstorj.io/storj/storagenode/reputation.(*Chore).Run.func1:61\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/storj/storagenode/reputation.(*Chore).Run:56\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:51\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2025-05-05T10:21:36Z ERROR contact:service ping satellite failed {"Process": "storagenode", "Satellite ID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU", "attempts": 9, "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:210\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2025-05-05 10:21:51,898 WARN received SIGTERM indicating exit request
2025-05-05 10:21:51,899 INFO waiting for processes-exit-eventlistener, storagenode, storagenode-updater to die
2025-05-05T10:21:51Z INFO Got a signal from the OS: "terminated" {"Process": "storagenode-updater"}
2025-05-05 10:21:51,900 INFO stopped: storagenode-updater (exit status 0)
2025-05-05T10:21:51Z INFO Got a signal from the OS: "terminated" {"Process": "storagenode"}
2025-05-05T10:21:51Z INFO contact:service context cancelled {"Process": "storagenode", "Satellite ID": "1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU"}
2025-05-05 10:21:52,412 INFO stopped: storagenode (exit status 0)
2025-05-05 10:21:52,412 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)
Please ignore: 2025-05-05T10:17:15Z INFO failed to sufficiently increase send buffer (I forgot to setup UDP, already fixed)
I’m particularly surprissed by 2025-05-05T10:17:11Z INFO Downloading versions. {“Process”: “storagenode-updater”, “Server Address”: “https://version.storj.io”} I made 3 necessary changes to config.yaml, here is what I have for version:
# server address to check its version against
# version.server-address: https://version.storj.io
version.server-address: https://version.qa.storj.io
server.use-peer-ca-whitelist: false is there as well changed storage2.trust.sources
Well - and even more important problem of never-ending errors about pinging satelite… Any ideas?
REMARK: my identity is not signed and (I suppose base on not being signed) there are 1 respectively 2 BEGIN sections instead of 2 and 3 (as described in identity creation topic)
Well, I was wrong originally. Error is still there, even I did what was described in the Linux Configuration for UDP - Storj Docs
Anyway - I added privileged into docker container and now it’s solved.
Have the same issue with version.server-address - it ignore the change in config.yaml .
The node starts and it says everything is ok in the GUI but trying to update it say 1.126.2 is the latest version. It is changed in the config.yaml but it still say https://version.storj.io
2025-05-05T15:24:55.631875881Z 2025-05-05T15:24:55Z INFO Anonymized tracing enabled {“Process”: “storagenode-updater”}
2025-05-05T15:24:55.633586517Z 2025-05-05T15:24:55Z INFO Running on version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.126.2”}
2025-05-05T15:24:55.634187947Z 2025-05-05T15:24:55Z INFO Downloading versions. {“Process”: “storagenode-updater”, “Server Address”: “https://version.storj.io”}
2025-05-05T15:24:56.070942184Z 2025-05-05T15:24:56Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode”, “Version”: “v1.126.2”}
2025-05-05T15:24:56.070986090Z 2025-05-05T15:24:56Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode”}
2025-05-05T15:24:56.084865702Z 2025-05-05T15:24:56Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.126.2”}
2025-05-05T15:24:56.084886174Z 2025-05-05T15:24:56Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”}
2025-05-05T15:24:57.086368839Z 2025-05-05 15:24:57,086 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-05-05T15:24:57.086470154Z 2025-05-05 15:24:57,086 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
This is docker so maybe we are not supposed to use docker with testnet?
The stefan-benten satellite does not exist:
testnet.satellite.stefan-benten.de
Server: 1.1.1.1
Address: 1.1.1.1#53
** server can’t find testnet.satellite.stefan-benten.de: NXDOMAIN
You may try to pass it with --version.server-address=https://version.qa.storj.io after the image name.
I don’t know how to do it properly, my attempt ended with:
unknown flag: --version.server-address
See 'docker run --help'.
Anyway I found that for whatever reason there is following ENV defined for container: VERSION_SERVER_URL (with value “https://version.qa.storj.io”). Perhaps defined when building image? Anyway, when I re-define it, it works… kind of 
I have this never-ending cycle of errors:
2025-05-06 06:17:56,903 INFO Set uid to user 0 succeeded
2025-05-06 06:17:56,905 INFO RPC interface 'supervisor' initialized
2025-05-06 06:17:56,906 INFO supervisord started with pid 1
2025-05-06 06:17:57,908 INFO spawned: 'processes-exit-eventlistener' with pid 30
2025-05-06 06:17:57,910 INFO spawned: 'storagenode' with pid 31
2025-05-06 06:17:57,911 INFO spawned: 'storagenode-updater' with pid 32
2025-05-06T06:17:57Z INFO Configuration loaded {"Process": "storagenode-updater", "Location": "/app/config/config.yaml"}
2025-05-06T06:17:57Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "contact.external-address"}
2025-05-06T06:17:57Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.private-address"}
2025-05-06T06:17:57Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "console.address"}
2025-05-06T06:17:57Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "healthcheck.details"}
2025-05-06T06:17:57Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.address"}
2025-05-06T06:17:57Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage2.trust.sources"}
2025-05-06T06:17:57Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "healthcheck.enabled"}
2025-05-06T06:17:57Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.use-peer-ca-whitelist"}
2025-05-06T06:17:57Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.email"}
2025-05-06T06:17:57Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.wallet-features"}
2025-05-06T06:17:57Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage.allocated-disk-space"}
2025-05-06T06:17:57Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "operator.wallet"}
2025-05-06T06:17:57Z INFO Anonymized tracing enabled {"Process": "storagenode-updater"}
2025-05-06T06:17:57Z INFO Running on version {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.126.2"}
2025-05-06T06:17:57Z INFO Downloading versions. {"Process": "storagenode-updater", "Server Address": "https://version.qa.storj.io"}
2025-05-06T06:17:57Z INFO Configuration loaded {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2025-05-06T06:17:57Z INFO Anonymized tracing enabled {"Process": "storagenode"}
2025-05-06T06:17:57Z INFO Operator email {"Process": "storagenode", "Address": "MYEMAIL@gmail.com"}
2025-05-06T06:17:57Z INFO Operator wallet {"Process": "storagenode", "Address": "0xMYWALLET"}
2025-05-06T06:17:58Z INFO server kernel support for server-side tcp fast open enabled. {"Process": "storagenode"}
2025-05-06T06:17:58Z INFO Current binary version {"Process": "storagenode-updater", "Service": "storagenode", "Version": "v1.126.2"}
2025-05-06T06:17:58Z INFO Download started. {"Process": "storagenode-updater", "From": "https://github.com/storj/storj/releases/download/v1.127.1/storagenode_linux_amd64.zip", "To": "/tmp/storagenode_linux_amd64.2518719296.zip"}
2025-05-06T06:17:58Z WARN version version not allowed/outdated {"Process": "storagenode", "current version": "1.126.2", "minimum allowed version": "v1.127.1"}
2025-05-06T06:17:58Z ERROR failure during run {"Process": "storagenode", "error": "Failed to check version: software outdated: outdated software version (v1.126.2), please update\n\tstorj.io/storj/private/version/checker.(*Service).CheckVersion:80\n\tmain.cmdRun:91\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:272", "errorVerbose": "Failed to check version: software outdated: outdated software version (v1.126.2), please update\n\tstorj.io/storj/private/version/checker.(*Service).CheckVersion:80\n\tmain.cmdRun:91\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:272\n\tmain.cmdRun:93\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:272"}
Error: Failed to check version: software outdated: outdated software version (v1.126.2), please update
storj.io/storj/private/version/checker.(*Service).CheckVersion:80
main.cmdRun:91
main.newRunCmd.func1:33
storj.io/common/process.cleanup.func1.4:392
storj.io/common/process.cleanup.func1:410
github.com/spf13/cobra.(*Command).execute:985
github.com/spf13/cobra.(*Command).ExecuteC:1117
github.com/spf13/cobra.(*Command).Execute:1041
storj.io/common/process.ExecWithCustomOptions:112
main.main:34
runtime.main:272
2025-05-06 06:17:58,411 WARN exited: storagenode (exit status 1; not expected)
2025-05-06 06:17:59,412 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-05-06 06:17:59,413 INFO spawned: 'storagenode' with pid 52
It tires to update to v1.127.1 and is (and when I log into console of this container, it reports 1.127.1), but something is missing to finish update. And it goes over and over again.
I have another problem - 0 bytes of ingress/egress/anything. Is it normal? Most probably it is as test is not paid nor guranteed to retain, but still a bit shame. I installed this test node as part of my new installation evaluation, so would be nice to have it with some data as well (e.g. to practice migration to another disk)
Edit: I have ~400K ingress and used space on disk. So yah, receiving data.
Tried passing the --version.server-address on the docker run command line but no difference so I gave up and made a standard node instead 
Most probably env variables take precedence. Try it my way:
docker run -d --restart unless-stopped --stop-timeout 300 \
-p 28967:28967/tcp \
-p 28967:28967/udp \
-p 127.0.0.1:14002:14002 \
-e WALLET="0xXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" \
-e EMAIL="user@example.com" \
-e ADDRESS="domain.ddns.net:28967" \
-e STORAGE="2TB" \
-e VERSION_SERVER_URL=https://version.qa.storj.io
--user $(id -u):$(id -g) \
--mount type=bind,source="<identity-dir>",destination=/app/identity \
--mount type=bind,source="<storage-dir>",destination=/app/config \
--name storagenode storjlabs/storagenode:latest
This was added:
-e VERSION_SERVER_URL=https://version.qa.storj.io
This is mean that you tried to provide it before the image name, not after. I.e. it should be
docker run -d --restart unless-stopped --stop-timeout 300 \
...
--name storagenode storjlabs/storagenode:latest \
--version.server-address=https://version.qa.storj.io
but also providing it as a variable should work too:
docker run -d --restart unless-stopped --stop-timeout 300 \
-e STORJ_VERSION_SERVER_ADDRESS=https://version.qa.storj.io \
...
--name storagenode storjlabs/storagenode:latest
But since you also found a separate one VERSION_SERVER_URL and it works - then you may use it.
My Test network node went offline. The docker logs (shown below) are indicating a 404 error on the last line.
I manually went to github and downloaded the latest version of the updater and the storage node and now it seems to be working.
The part that bothers me is that before I noticed my QA node was malfunctioning, it seems to have been stuck in an infinite loop downloading something from github over and over. I don’t want them blocking me for abuse.
17250K .......... .......... .......... .......... .......... 99% 11.6M 0s
17300K .......... .......... .......... .......... .......... 99% 11.4M 0s
17350K .......... .......... .......... .......... .......... 99% 11.6M 0s
17400K .......... ......... 100% 15.6M=1.6s
2025-11-01 17:35:28 (10.9 MB/s) - '/tmp/storagenode-updater.zip' saved [17837292/17837292]
downloading storagenode-updater
--2025-11-01 17:35:30-- https://version.qa.storj.io/processes/storagenode-updater/suggested/url?os=linux&arch=amd64
Resolving version.qa.storj.io (version.qa.storj.io)... 35.208.199.238
Connecting to version.qa.storj.io (version.qa.storj.io)|35.208.199.238|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 96 [text/plain]
Saving to: 'STDOUT'
0K 100% 247M=0s
2025-11-01 17:35:30 (247 MB/s) - written to stdout [96/96]
--2025-11-01 17:35:30-- https://github.com/storj/storj/releases/download/v1.141.1-rc/storagenode-updater_linux_amd64.zip
Resolving github.com (github.com)... 140.82.113.4
Connecting to github.com (github.com)|140.82.113.4|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2025-11-01 17:35:31 ERROR 404: Not Found.
If you’re running QA builds… maybe that version simply got pulled for some reason? Usually stuff like that is fixed in a day or so.
Hello @Mark,
Welcome back!
Shared with the team.
It should be marked as pre-release and can be downloaded. Could you please check?