It supports direct messages, point to my avatar and click the Message button.
please give me a result of mtr command to version.storj.io and to the GitHub (because it downloads a new version from GitHub)).
Seems this subnet belongs to Iran and I believe that it’s in the US sanctioned countries list…
This screenshot shows you misspelled version.storj.io
2 Likes
Please post mtr to the GitHub too, please use the address from the log.
Am I getting unblocked or whats the status now ?
Devs have applied a fix, please try to access version.storj.io now.
works now, already deployed, thank you
3 Likes
I restart Docker and the node does not start.
there are pings, there is a route, but there is no answer!
I ran into this problem today!
Hello @rem1,
Welcome to the forum!
Please provide an error from the logs: How do I check my logs? - Storj Docs
docker logs --follow --tail 100 st25
downloading storagenode-updater
–2024-02-02 06:00:14-- https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=amd64
Resolving version.storj.io (version.storj.io)… 34.173.164.90
Connecting to version.storj.io (version.storj.io)|34.173.164.90|:443… connected.
Do you have any error after “connected”?
If not or a timeout error, your IP may be blocked by GCP. The only way is to change your IP.
And you don’t have another option why is this happening? what is GCP
Everything has always worked well, only today I noticed this problem
GCP = Google Cloud Provider.
Unfortunately there is no other way. I forced to change my IP because of this reason. Their blocking “feature” is not configurable.
The problem is with the new ip!
Aside from IP incorrectly being defined, Google Cloud also seems to track things like VPN usage.
e.g. Somebody accessed data in/from a sanctioned country on that IP using VPN and it can be flagged as “potentially related to a sanctioned country”. This of course can happen accidentally, e.g. going on a vacation in a sanctioned country and then accessing your home machine via a VPN. Also, this might not have been you, maybe the IP was previously used by a botnet, or it’s a shared IP between multiple people or some virus happened to access through VPN.
All of this is speculation from my side, because I don’t know the internal details on how GCP handles this kind of blocking.
Speculation based on Reddit - Dive into anything
2 Likes
Mine was a static and worked perfectly for the last 3 years, and there were only storagenodes.
I started experiencing this problem today as well. Is there any way to proxy requests to version.storj.io so that the update works correctly? My node went down due to an automatic update and I need some solution to get it working again.
storagenode | downloading storagenode-updater
storagenode | --2024-02-15 05:52:48-- https://version.storj.io/processes/storagenode-updater/minimum/url?os=linux&arch=amd64
storagenode | Resolving version.storj.io (version.storj.io)... 34.173.164.90
storagenode | Connecting to version.storj.io (version.storj.io)|34.173.164.90|:443... connected.
I’ve tried to implement my own proxied version of https://version.storj.io, and wanted to use it in my storjnode instance. I’ve changed version.server-address parameter in config.yaml, and also changed command section in my docker-compose to --version.server-address=https://storj-version-proxy.protolaunch.workers.dev, but software still tries to use version.storj.io.