1.155.8 broken storagenode-updater_linux_amd64.zip link

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

Hi there.

Is autoupdate to latest storagenode image safe? My node just stop working, because it attempting to update from non-existing image.

https://github.com/storj/storj/releases/download/v1.155.8/storagenode-updater_linux_amd64.zip → ERROR 404: Not Found.

Have you please somebody more information regarding the problem?

Thank you!

My nodes ended-up down with updater spaming log (stil over and over the same):

2026-06-12 07:13:12 (11.3 MB/s) - '/tmp/storagenode-updater.zip' saved [18105000/18105000]
downloading storagenode-updater
--2026-06-12 07:13:23--  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%  248M=0s
2026-06-12 07:13:24 (248 MB/s) - written to stdout [93/93]
--2026-06-12 07:13:24--  https://github.com/storj/storj/releases/download/v1.155.8/storagenode-updater_linux_amd64.zip
Resolving github.com (github.com)... 140.82.112.4
Connecting to github.com (github.com)|140.82.112.4|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2026-06-12 07:13:24 ERROR 404: Not Found.
downloading storagenode-updater
--2026-06-12 07:13:30--  https://version.storj.io/processes/storagenode-updater/minimum/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%  316M=0s
2026-06-12 07:13:43 (316 MB/s) - written to stdout [93/93]
--2026-06-12 07:13:43--  https://github.com/storj/storj/releases/download/v1.152.6/storagenode-updater_linux_amd64.zip
Resolving github.com (github.com)... 140.82.113.3
Connecting to github.com (github.com)|140.82.113.3|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://release-assets.githubusercontent.com/github-production-release-asset/128089774/97fed598-fb26-4e0c-a571-3496c0302cca?sp=r&sv=2018-11-09&sr=b&spr=https&se=2026-06-12T08%3A07%3A57Z&rscd=attachment%3B+filename%3Dstoragenode-updater_linux_amd64.zip&rsct=application%2Foctet-stream&skoid=96c2d410-5711-43a1-aedd-ab1947aa7ab0&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skt=2026-06-12T07%3A07%3A39Z&ske=2026-06-12T08%3A07%3A57Z&sks=b&skv=2018-11-09&sig=%2BiH7lc54JSuZhsgJCRDKZ9uqPNV8DSiQN7513BQnrNU%3D&jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmVsZWFzZS1hc3NldHMuZ2l0aHVidXNlcmNvbnRlbnQuY29tIiwia2V5Ijoia2V5MSIsImV4cCI6MTc4MTI1MDE3NSwibmJmIjoxNzgxMjQ4Mzc1LCJwYXRoIjoicmVsZWFzZWFzc2V0cHJvZHVjdGlvbi5ibG9iLmNvcmUud2luZG93cy5uZXQifQ.kj4vrMnrgS1aIw3nfq68BCyzTfeJbOqB83_9i4yqqx0&response-content-disposition=attachment%3B%20filename%3Dstoragenode-updater_linux_amd64.zip&response-content-type=application%2Foctet-stream [following]
--2026-06-12 07:13:44--  https://release-assets.githubusercontent.com/github-production-release-asset/128089774/97fed598-fb26-4e0c-a571-3496c0302cca?sp=r&sv=2018-11-09&sr=b&spr=https&se=2026-06-12T08%3A07%3A57Z&rscd=attachment%3B+filename%3Dstoragenode-updater_linux_amd64.zip&rsct=application%2Foctet-stream&skoid=96c2d410-5711-43a1-aedd-ab1947aa7ab0&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skt=2026-06-12T07%3A07%3A39Z&ske=2026-06-12T08%3A07%3A57Z&sks=b&skv=2018-11-09&sig=%2BiH7lc54JSuZhsgJCRDKZ9uqPNV8DSiQN7513BQnrNU%3D&jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmVsZWFzZS1hc3NldHMuZ2l0aHVidXNlcmNvbnRlbnQuY29tIiwia2V5Ijoia2V5MSIsImV4cCI6MTc4MTI1MDE3NSwibmJmIjoxNzgxMjQ4Mzc1LCJwYXRoIjoicmVsZWFzZWFzc2V0cHJvZHVjdGlvbi5ibG9iLmNvcmUud2luZG93cy5uZXQifQ.kj4vrMnrgS1aIw3nfq68BCyzTfeJbOqB83_9i4yqqx0&response-content-disposition=attachment%3B%20filename%3Dstoragenode-updater_linux_amd64.zip&response-content-type=application%2Foctet-stream
Resolving release-assets.githubusercontent.com (release-assets.githubusercontent.com)... 185.199.110.133, 185.199.108.133, 185.199.111.133, ...
Connecting to release-assets.githubusercontent.com (release-assets.githubusercontent.com)|185.199.110.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 18105000 (17M) [application/octet-stream]
Saving to: '/tmp/storagenode-updater.zip'
     0K .......... .......... .......... .......... ..........  0%  384K 46s

Because there really is no updater file on the github :slight_smile:
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 am facing the same issue. How do I fix it?

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

Oh not another one … you can do as I mentioned on my post yesterday about 1.155.4

Delete the files from the Bin file, from the node data directory , should be outside of where the “storage” directory is

Oh.. version.storj has been updated

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

When the node starts, could you check you will also have an “unclean shutdown detected” in the logs?

@Andrii @Alexey @elek

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

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.

My node is now working, but I was down some couple of minutes, maybe one hour :frowning: .

I would be glad, if somebody from developers can provide some explantion.

3 docker nodes updated to 1.55.8 and working, fully migrated to hashstore and no dedicated disk

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?

But storagenode-updater_linux_amd64.zip is not in this release.

Good question, I saw the error from the image logs:

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).

The version.storj.io has been updated, the problem was actually with the updater, not with the node.
Devs are working on a fix