Updater attempting to download release from bad url

Node Operators troubleshooting
1

It looks like the updater is looking for a release with a bad URL, causing it to be offline

node-1 | downloading storagenode-updater
node-1 | --2025-09-04 02:35:46-- https://version.storj.io/processes/storagenode-updater/suggested/url?os=linux&arch=amd64
node-1 | Resolving version.storj .io (version.storj .io)… 34.173.164.90
node-1 | Connecting to version.storj .io (version.storj .io)|34.173.164.90|:443… connected.
node-1 | HTTP request sent, awaiting response… 200 OK
node-1 | Length: 94 [text/plain]
node-1 | Saving to: ‘STDOUT’
node-1 |
node-1 | 0K 100% 309M=0s
node-1 |
node-1 | 2025-09-04 02:35:46 (309 MB/s) - written to stdout [94/94]
node-1 |
node-1 | --2025-09-04 02:35:46-- https://github.com/storj/storj/releases/download/vv1.136.4/storagenode-updater_linux_amd64.zip
node-1 | Resolving github. com (github. com)… 140.82.113.4
node-1 | Connecting to github. com (github. com)|140.82.113.4|:443… connected.
node-1 | HTTP request sent, awaiting response… 404 Not Found
node-1 | 2025-09-04 02:35:47 ERROR 404: Not Found.
node-1 |

Can someone fix the updater URLs?

1 Like
2

for some reason, on version.storj.io
“https://github.com/storj/storj/releases/download/vv1.136.4/storagenode_{os}_{arch}.zip"},"rollout”: there is doble v in name so updater cant update

1 Like
3

The issue seems to be the URL being issued by the versions server has two 'v’s in the version number.

IE, the bad URL:
https://github.com/storj/storj/releases/download/vv1.136.4/storagenode-updater_linux_amd64.zip

The good URL:
https://github.com/storj/storj/releases/download/v1.136.4/storagenode-updater_linux_amd64.zip

1 Like
4

Found a quick and somewhat questionable solution to the issue at hand to get the node back online.

I downloaded both the storagenode-updater and the storagenode binaries from the correct URLs and unziped them to the config/bin folder. The node started up on version 1.136.4

3 Likes
5

I reported this error and got response than team will fix it.

1 Like
6

It should be fixed already, could you please check?

4 Likes
7

working ok for me, than you.

1 Like