Network error with `uplink share`

Hey all,

For the last couple hours I’ve been getting failures when running uplink share. Nothing in my code has changed so I’m assuming it’s likely related to a failing Storj API? Full stack trace below:

Failing command: uplink share --url --readonly --access [access here] sj://[path here]

Stack trace:

uplink: dial to auth service failed: rpc: EOF
	storj.io/uplink/edge.(*Config).RegisterAccess:64
	main.RegisterAccess:225
	main.(*cmdShare).Execute:115
	main.(*external).Wrap:123
	github.com/zeebo/clingy.(*Environment).dispatchDesc:126
	github.com/zeebo/clingy.(*Environment).dispatch:53
	github.com/zeebo/clingy.Environment.Run:34
	main.main:26
	runtime.main:255

Hello @corbt ,
Welcome to the forum!

Seems auth service for your location is failing to register an access grant on GatewayMT.
What is geographical location of the device with uplink?
What is version of uplink? (uplink version)

There was an outage but it seems to work now. Please try again.

2 Likes

Yeah the jobs have gone through now. Where do you track and report outages? https://status.storj.io/ stayed green throughout the process, which is concerning.

Hi Corbt,

Thanks for reporting this to us. You were looking in the right place. We do post outages there. Not every outage is automated to report there and at times we have to triage and then add the detail manually and/or post date it. It’s our intention to give you up to date information so you aren’t wondering if it’s something on your end versus ours. We continue to refine this process and make it better, and we appreciate your patience and understanding as we continue to improve it.

4 Likes

Thanks, appreciate the support!

1 Like