The proxy likely will not help, only change of IP.
It looks like my ISP was blocking this address or IP. At that time, I’ve found that you can change VERSION_SERVER_URL variable to any domain, where you deployed a proxy version of version.storj.io. After some time, the URL was unblocked on my ISP after some time, and the issue was gone.
1 Like
Hello,
I’m facing the same issue starting from today.
storagenode4 | downloading storagenode-updater
storagenode4 | --2025-02-21 16:31:50-- https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=amd64
storagenode4 | Resolving version.storj.io (version.storj.io)… 34.173.164.90
storj-exporter4 | 2025-02-21 16:31:51 [WARNING]: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘NewConnectionError(’<urllib3.connection.HTTPConnection object at 0x7c126eee3850>: Failed to establish a new connection: [Errno 111] Connection refused’)‘: /api/sno/estimated-payout
storagenode4 | Connecting to version.storj.io (version.storj.io)|34.173.164.90|:443… failed: No route to host.
storagenode4 | http://: Invalid host name.
storj-exporter4 | 2025-02-21 16:31:53 [WARNING]: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘NewConnectionError(’<urllib3.connection.HTTPConnection object at 0x7c126eee3a90>: Failed to establish a new connection: [Errno 111] Connection refused’)‘: /api/sno/estimated-payout
storj-exporter4 | 2025-02-21 16:31:53 [INFO]: Registering payout collector
storj-exporter4 | 2025-02-21 16:31:53 [WARNING]: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘NewConnectionError(’<urllib3.connection.HTTPConnection object at 0x7c126eeeb0a0>: Failed to establish a new connection: [Errno 111] Connection refused’)': /api/sno/estimated-payout
storagenode4 exited with code 0
How can I solve this ?
Thanks
@Alexey Hello,
the updater error was due to a tenatative to fix something else… I renamed some files under bin.
Once I put it back I’m still with the old erro
storagenode4 | 2025-02-21 16:41:33,879 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
storagenode4 | 2025-02-21 16:41:33,880 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
storagenode4 | 2025-02-21 16:41:33,881 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
storagenode4 | 2025-02-21T16:41:33Z ERROR Error retrieving version info. {“Process”: “storagenode-updater”, “error”: “version checker client: Get "https://version.storj.io": dial tcp 34.173.164.90:443: connect: no route to host”, “errorVerbose”: “version checker client: Get "https://version.storj.io": dial tcp 34.173.164.90:443: connect: no route to host\n\tstorj.io/storj/private/version/checker.(*Client).All:68\n\tmain.loopFunc:20\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tmain.cmdRun:139\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\tstorj.io/common/process.ExecWithCustomConfigAndLogger:77\n\tmain.main:22\n\truntime.main:272”}
still no route to host 
any idea ?
thanks
The network is broken, you need to fix it. If you used a snap version of docker, you need to remove it and install the native: Install | Docker Docs
Yes, I provided the solution in another thread ! network was broken during the upgrade.
To fix I had to flush iptables (reset to default) and then just restart docker to recreate docker’s iptables entries (or just restart)
Best regards