Testnode sudenly fails to start

Node Operators troubleshooting
,
1

so my compose/stackfile have run fine for days now

version: "3.7"
services:
  testnode:
    container_name: testnode
    restart: always
    stop_grace_period: 300s
    image: storjlabs/storagenode:latest
    ports:
      - "28970:28967/tcp"
      - "28970:28967/udp"
      - "14005:14002/tcp"
    volumes:
      - type: bind
        source: /mnt/sde1/Storj/testnode/Identity/
        target: /app/identity
      - type: bind
        source: /mnt/sde1/Storj/testnode/Storage/
        target: /app/config
    environment:
      - WALLET=****
      - EMAIL=****
      - ADDRESS=****:28970
      - STORAGE=500GB
      - VERSION_SERVER_URL=https://version.qa.storj.io

but it does not start and i think it might be due to github…. anyone else experienced the same?

root@bo-omv:~# docker logs --tail 20 testnode
2025-11-13 21:28:52 (5.00 MB/s) - '/tmp/storagenode-updater.zip' saved [17831003/17831003]

downloading storagenode-updater
--2025-11-13 21:28:54--  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%  151M=0s

2025-11-13 21:28:54 (151 MB/s) - written to stdout [96/96]

--2025-11-13 21:28:54--  https://github.com/storj/storj/releases/download/v1.142.0-rc/storagenode-updater_linux_amd64.zip
Resolving github.com (github.com)... 140.82.121.4
Connecting to github.com (github.com)|140.82.121.4|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2025-11-13 21:28:55 ERROR 404: Not Found.

root@bo-omv:~#
2

The version server is pointing to a version that doesn’t exist. :roll_eyes:

3

@Alexey did someone at Storj make a “booboo” ?

4

at least the emails work, got 4 so one from each satelitte i guess

5

also it seems that only us1.storj.io is doing any vetting

what is going on?

EDIT: for now i have removed - VERSION_SERVER_URL=https://version.qa.storj.io from the compose file…. now at least it runs on v1.141.2

6

I shared this with the team.

7

Thanks for the report.

version.qa.storj.io should be fixed by now. It points to latest version v1.142.3.

2 Likes
8

yep worked fine, now the online % just has to climp due to the downtime :smiley: :rofl: