rpc: tcp connector failed: rpc: EOF
storj.io/common/rpc.HybridConnector.DialContext.func1:190
What’s uplink version?
uplink_windows_amd64 cli
Do I need to deploy Storj Testnet?
Of course not, unless you want to test your use case against the Storj network locally.
For the Global network it should work out-of-the-box
Please give me a version:
./uplink version
Added this info for the team. Thanks!
You may enable a lexicographic ordering in a different way:
uplink access create --unencrypted-object-keys
You would be asked for a satellite URL (it should include the satellite ID, hostname and the port), the API key and the passphrase. See Generating and Managing Access Grants - Storj Docs how to create the API key creds.
You may also store it as an access grant if you would add an option --import-as:
uplink access create --unencrypted-object-keys --import-as my-unencrypted-paths
The name of the access would be my-unencrypted-paths in this case.
So, you may register S3 credentials:
uplink access register --access my-unencrypted-paths
Hi @wind,
Thank you for reaching out. To provide the best support we can, we’d need a few more details. Would you mind filling this in?
**Description**
<!--
Provide a more detailed introduction to the issue itself, and why you consider it to be a bug
-->
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Steps to reproduce the issue:**
<!-- Provide a link to a live example, or an unambiguous set of steps to -->
<!-- reproduce this bug. Include code to reproduce, if relevant -->
<!-- You can open a PR with a failing test instead -->
1.
2.
3.
**Describe the results you expected:**
**Describe the results you received:**
**Possible Fix**
<!--- Not obligatory, but suggest a fix or reason for the bug -->
**Additional information you deem important (e.g. issue happens only occasionally):**
**Logs:**
(paste your logs here)
**Your environment**
<!--- Include as many relevant details about the environment you experienced the bug in -->
- Operating system and version:
- Additional environment details (Raspberry PI, Docker, VMWare, etc.):
Does this command works?
.\uplink ls
I suspect the same network issue as in other your threads. Do you have a filtering firewall or blocking devices like PiHole?
If so, could you please disable them or allow to connect to any IP and any ports?
This command is also invalid, but it is possible to use aws s3 cli.
Same error: rpc: tcp connector failed: rpc: EOF
storj.io/common/rpc.HybridConnector.DialContext.func1:190
This only confirm my suspicion - S3 protocol uses only 443 port and one instance closest to you.
The native Storj protocol is a p2p protocol, it uses up to 100 connections per segment to different IPs and different ports across the world.
Could you please try to use a mobile internet? Or use a VPN service, if you are from China/Russia?
Thank you very much, the problem is solved. I tried to change the VPN node and it worked.
2 Likes
Please also try this method for other cases too.
Or you may always use only S3, it’s up on you.
Ok, all the problems encountered so far have been resolved. Thank you very much.
2 Likes