One of my node in docker is trying to update to 1.155.8 and it is looping because the download link is missing storagenode-updater_linux_amd64.zip
Checking GitHub and it is missing there as well
--2026-06-12 06:58:44-- https://version.storj.io/processes/storagenode-updater/suggested/url?os=linux&arch=amd64
Resolving version.storj.io (version.storj.io)... 35.209.24.65
Connecting to version.storj.io (version.storj.io)|35.209.24.65|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 93 [text/plain]
Saving to: 'STDOUT'
0K 100% 174M=0s
2026-06-12 06:58:45 (174 MB/s) - written to stdout [93/93]
--2026-06-12 06:58:45-- https://github.com/storj/storj/releases/download/v1.155.8/storagenode-updater_linux_amd64.zip
Resolving github.com (github.com)... 140.82.114.3
Connecting to github.com (github.com)|140.82.114.3|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2026-06-12 06:58:45 ERROR 404: Not Found.
Edit: Work around, manually download the newest storagenode file off the github page, and use the updater file in the 1.155.4 and overwrite your bin folder
Because there really is no updater file on the github
Wait node will start with error:
ERROR Error updating service. {“process”: “storagenode-updater”, “service”: “storagenode-updater”, “error”: “bad status: 404 Not Found”, “errorVerbose”: "bad status: 404 Not Found
i think as soon as they uploaded it a bunch of nodes updated. all 3 of mine, even in different locations hit at the same time, that 's not common. Mine were down about 15 mins
Just wait. Node will start with error
ERROR Error updating service. {“process”: “storagenode-updater”, “service”: “storagenode-updater”, “error”: “bad status: 404 Not Found”, “errorVerbose”: "bad status: 404 Not Found
I have same issue with one of my nodes. Most of the nodes just restarted several times, but recovered. One node has crashed and are now not able to start up again.
Hello @Adavan,
Welcome back! v1.155.8 was published on June 11, 2026 at 18:41:53 UTC
So it should be available since then, maybe it’s not updated on your closest CDN?
When I attempted to download the same URL on different machine, unfortunately, I got same error message. Next I start looking for the URL and got same, like @mr.Viking:
So, maybe some glitch in GitHub pipelines? (to updater goes wrong version, which was deleted or not existed in the time, I am not sure).