kar1
March 16, 2023, 4:54am
1
When I tried to setup uplink it works well but at the last shows this error.
Imported access "main" to "C:\\Users\\Karan102\\AppData\\Roaming\\Storj\\Uplink\\access.json" Switched default access to "main" Would you like S3 backwards-compatible Gateway credentials? (y/N): y uplink: register access for edge services failed: access grant: disallowed satellite "1WsExd5kCt1RqkYNpZFF1HJwBzmWjs8zSs6ju7NDJsGzfe66UX@127.0.0.1:10000" storj.io/uplink/edge.(*Config).RegisterAccess:91 main.RegisterAccess:227 main.(*cmdAccessSetup).Execute:104 main.(*external).Wrap:353 github.com/zeebo/clingy.(*Environment).dispatchDesc:106 github.com/zeebo/clingy.(*Environment).dispatch:52 github.com/zeebo/clingy.(*Environment).dispatchDesc:59 github.com/zeebo/clingy.Environment.Run:34 main.main:35 runtime.main:250
Alexey
March 16, 2023, 5:07am
2
The register access grant command requires working Edge services, authservice and gateway-mt specifically.
Did you manage to setup them in this thread:
Hello @kar1 ,
There are some additional steps you’ll have to take to get the file browser to work.
Install the Storj Edge Services.
Clone the storj/gateway-mt repository.
While within the directory you cloned it into, run go install -v ./....
Destroy and restart your local Storj network.
You must run storj-sim using the storj-sim network run --no-gateways command.
Get your local satellite’s node URL.
Run storj-sim network env SATELLITE_0_URL.
Run authservice.
Replacing SAT_NODE_URL w…
if not, the register will not work too.
I invited team members to that thread for storj-sim and Edge services, since I have no knowledge how to integrate Edge to storj-sim.
However, I know, that Edge services are working in storj-up .
kar1
March 16, 2023, 6:38am
3
Hello @Alexey
No I didnt get solution in this thread too
It would be great thanks …
kar1
March 17, 2023, 5:23am
4
Hello @Alexey I get the solution of previous thread.
But this Uplink Setup Error is still disturbing me please help me to solve this issue…
@jeremy
Alexey
March 17, 2023, 8:18am
5
You need to configure uplink to use your local Auth service instead of ours
uplink setup [--auth-service string] [--force] [--use]
--auth-service string If generating backwards-compatible S3 Gateway credentials, use this auth service (default https://auth.storjshare.io)
It also should be supported as an option in the config.yaml
(placed to the location for --legacy-config-dir
option).
You may check default locations like this:
uplink setup --help --advanced | grep "legacy-config-dir"
or for PowerShell
uplink setup --help --advanced | sls "legacy-config-dir"
1 Like
kar1
March 17, 2023, 8:54am
6
Hello @Alexey
What should be input for --auth-service?
When can I find it?
Alexey
March 17, 2023, 8:58am
7
It’s an listening address for your Auth service, I believe it’s http://localhost:7772
in your setup
@kar1 The satellite is able to fetch Gateway credentials from port 7772 because you specified --listen-addr :7772 when executing authservice run. This allows authservice to handle any requests directed to http://localhost:7772.
1 Like
kar1
March 17, 2023, 9:06am
8
Yes but I have reconfigure all and now my updated setup is
authservice run ^
--allowed-satellites 1Yfzd9me7ztdNAYhNu9New4MEVTv6RA1DrLMWmwhHDoykVcg8h@127.0.0.1:10000 ^
--auth-token my-test-auth-token ^
--endpoint http://localhost:8002 ^
--listen-addr :8000 ^
--kv-backend badger://
gateway-mt run ^
--auth.token my-test-auth-token ^
--auth.base-url http://localhost:8000 ^
--domain-name localhost ^
--server.address localhost:8002 ^
--insecure-disable-tls
kar1
March 17, 2023, 9:07am
9
@Alexey
I have run this
uplink setup --auth-service http://localhost:8000
but it gives me an error like this:
uplink: dial to auth service failed: rpc: address http://localhost:8000: too many colons in address
What is that?
Alexey
March 18, 2023, 1:01pm
10
Did you use a correct address? I thought it has a port 8001
1 Like
kar1
March 20, 2023, 4:40am
12
Hello @Alexey
There is no such configuration donefor port 8001 I have used 8000 and 8002 for authservice and gateway-mt run
kar1
March 23, 2023, 9:20am
13
Hello @Alexey
Any suggetion on this error.
Alexey
March 25, 2023, 2:42am
14
You need to add your satellite to the allowed list on authservice either with an argument --allowed-satellites=1WsExd5kCt1RqkYNpZFF1HJwBzmWjs8zSs6ju7NDJsGzfe66UX@127.0.0.1:10000
in your authservice run
command or with an option in the authservice’s config.yaml
file:
allowed-satellites: 1WsExd5kCt1RqkYNpZFF1HJwBzmWjs8zSs6ju7NDJsGzfe66UX@127.0.0.1:10000
1 Like
kar1
March 27, 2023, 4:22am
15
So I have to do uplink setup after run authservice …?
@Alexey
Alexey
March 27, 2023, 5:10am
16
If you have already setup it - you may just try to use it. Make sure that authservice has this option loaded (you need to restart it).
1 Like