downloading storagenode-updater
Connecting to version.storj.io (version.storj. io)|208.31.254.33|:443… failed: Connection timed out.
Connecting to version.storj.io (version.storj. io)|2001::c760:3e11|:443… failed: Cannot assign requested address.
Retrying.
In some places，storj can not be connected. So how to connect other node?
or these information can be downloaded from p2p?
Domain is not always reliable。 it can be banned easily.
Hello @bugx,
Welcome to the forum!
If your IP is blocked by cloud providers, include Google, then your node likely will not be able to serve customers requests, so you need to change your public IP to the not blocked one.
This is especially true for IPs from Hetzner for some reason, maybe their service is often used for abuse or malware distribution, I do not know.
It’s not banned by cloud provider. In China, the domains of storJ.io all be banned by Great Fire wall.
I think the meaning of such decentralized storage is to be unblocked. We can choose to register on any satellite.
the satellite is only 1/3 of the problem, your node serves requests from customers across the globe, so you need that your node is available for them.
Perhaps VPN with port-forwarding feature is the only option. You may use portmap.io, ngrok, PIA, AirVPN, PureVPN, etc.
You may not understand what I mean. I think decentralized storage services should not rely on domain names and unified node servers. For example, if I am in China, I can set up a node in China to provide storage services. Through the p2p protocol, I can synchronize data to other node servers in the world. Because the blockade only targets domain names.
The Storj p2p is different from bittorrent, nodes accepts connections from the customers, so your node must be available for the customer. If you do not have a public IP (your node is not exposing port on the available IP for the customer), it will be considered as offline.
It’s not related to usage of domain names, you may use a pure IP, but if it’s dynamic, you would be forced to update the node’s configuration every time when your IP is changed. To avoid that you would use DDNS services.
Nodes in the Storj network doesn’t relay traffic between each other to proxy traffic for nodes behind a firewall, like it happening in bittorrent, because bandwidth is paid, but who will pay for the used bandwidth to the relay nodes?
We have had a relay possibility in a previous version of the Storj network, but Node Operators always asked the same question - “my node is relaying traffic for firewalled nodes, why it reduces my available bandwidth and earnings, why is it not paid?”, and firewalled nodes didn’t share earnings with the relay nodes. As a result, many operators turned off relays.
In the current version of the Storj network we did not implement the relay possibility for many reasons, include protection of customers data: we filter out nodes behind /24 subnet of public IPs to do not put more than a one segment of the file to the same location, with enabled relay all relay nodes and proxied nodes will be considered as working from the same subnet and only one node will be selected, reducing bandwidth and earnings for relay nodes. So Operators will likely disable the relay anyway.
The proxied nodes are not reliable available, this will force to repair pieces more often than needed, these nodes usually have a lower transfer speed for the customer, slowing down the overall transfer for the customers.
I’m very glad you could reply to my question. I got you. I now have a fixed IP and domain name, and can provide storage services to users. But my node server cannot connect to storj.io. Am I also unable to set up a storage service? All storage links must be centered on storj io? What I mean is that storJ is a decentralized storage service, and new nodes can be registered on any node that already exists in the network. Users can store on the APP established on any node. Behind each node are connected some storage servers. Even if this node cannot communicate with storj io, as long as it can communicate with other nodes on the chain and ensure that there are 80 storage servers that meet the conditions. It’s just available.
usually you need either a static public IP or DDNS domain and dynamic public IP, but if your static IP would suddenly change - you will be ok.
That’s a problem, seems something is blocking access to it (we do not block IPs not related to OFAC), communication with other nodes would not help, if either your node cannot connect satellites and other Storj services or the satellite cannot connect your node - your node will not be suggested to the customers.
So I believe you have only one option - is to use VPN with port forwarding feature or something like this:
It’s also possible to add real IPs of our services to the hosts file and maybe it could help to evade blocking.
