Wasabi auth error, need level 1 support

Help and Support
1

Installed via mac brew today and trying to get up to speed, docs are overwhelming and just trying to get a simple start has been frustrating. just wanted to have ability to sync some folders in the future or just copy via terminal instead of launching gui tools.

Similar to this closed ticket, i am getting this error, having run config interactive for wasabi prior

ERROR : : error listing: InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records.

in that ticket solution said to add session_token = XXXX to config but that seemed pointless effort

using same key I generated/use for my gui client so i know it works

rclone v1.55.0 -- mac os sierra

  • os/type: darwin
  • os/arch: amd64
  • go/version: go1.16.3
  • go/linking: dynamic
  • go/tags: none

wasabi us-east-1

I tried copy then a simpler:

rclone lsd wasabi:

clone copy ./localfolder wasabi:/test/folder

with different path attempts and flags --dry-run and -i

obv if getting auth error nothing will work.

type = s3
provider = wasabi
env_auth = false
access_key_id =  {redacted}
secret_access_key =  {redacted}
region = us-east-1
location_constraint = us-east-1
acl = private
2

hi,
i use wasabi all the time.

rclone posts the error it got from wasabi.

login to wasabi and double check.
could be a simple copy/paste problem or your rclone config file is corrupted.

3

i had a window open during my testing so i could make sure if anything was happening.

can you verify my command syntax, in particular the source/dest format? I'm sure config is fine

4

if the access key id is not accepted by wasabi, no command will work.

you already tried rclone lsd wasabi: and that failed.
can you post a debug output of that?

5

i tried a new key to be sure and same error, i will see how to get a log output
i also verified my settings as per the wasabi config faq here

DEBUG : rclone: Version "v1.55.0" starting with parameters ["rclone" "lsd" "wasabi:" "-vv" "--log-file=./clog.txt"]
DEBUG : Creating backend with remote "wasabi:"
ERROR : : error listing: InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records.
	status code: 403, request id: ..., host id: ...
DEBUG : 6 go routines active
Failed to lsd with 2 errors: last error was: InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records.
	status code: 403, request id: ..., host id: ...```


user has read and write access. does it need any other permissions? it's in the bucket group i made for this computer to use.
6

so this is a user you created?
if true, have you tried using the root access key id?

7

well i tried with my user i use on my gui client, and then made this new user to see if that changed anything and it didn't. maybe there's some problem with my platform

8

what gui client?

try an older version https://downloads.rclone.org/v1.54.1/

try --dump responses for more detail

9

i use msp360 and mountain duck. i will try connecting to non wasabi system to see if that differs.

ahh.. your dump shows this line!

Host: s3.us-east-1.amazonaws.com

that's not wasabi how did that happen???

10

nothing better than a dump.
no idea how that happened.

can you post the current config, redact id/secrets.
i noticed that you used

region = us-east-1
location_constraint = us-east-1

i use endpoint = s3.us-east-2.wasabisys.com

11

ok this helped... so now the only error i got in log was
ERROR : : error listing: MissingEndpoint: 'Endpoint' configuration is required for this service

i had put region and endpoint as you used endpoint above, so maybe that was my mistake will try again

12

oh you are using zone 2, i am using 1, so edited that.

still complaining about endpoint whatever i put there, but at least we are talking to wasabi now

2021/04/09 17:16:12 DEBUG : Creating backend with remote "wasabi:"
2021/04/09 17:16:12 ERROR : : error listing: MissingEndpoint: 'Endpoint' configuration is required for this service
2021/04/09 17:16:12 DEBUG : 4 go routines active
2021/04/09 17:16:12 Failed to lsd with 2 errors: last error was: MissingEndpoint: 'Endpoint' configuration is required for this service

13

https://wasabi-support.zendesk.com/hc/en-us/articles/360015106031-What-are-the-service-URLs-for-Wasabi-s-different-storage-regions-

here is my config file.
i used to use zone1 but there was a time there are a lot of issues and slowdowns.
once they added zone 2 i switched that

rclone config show wasabi01:
--------------------
[wasabi01]
type = s3
provider = Wasabi
access_key_id = 
secret_access_key = 
endpoint = s3.us-east-2.wasabisys.com
14

ah ok ENDPOINT not the other terms the config tool was prompting me for

commented out REGION and LOCATION. worked.

THANK YOU marked as solution

15

now to debug my copy syntax :confused:

16

rclone copy ./localfolder wasabi:/test/folder
the problem is that bucket names have to be unique, there cannot be two buckets with the same name for the entire wasabi.com domain name, as it uses dns.

17

ok this worked for a file:

rclone copy .file.txt wasabi:mybuckname/test/file --dry-run

18

so weird when i turn off dry run it tries to do amazon again

readded region... [nope that failed, removed and lsd works again]

copy giving error, saying i don't have permission to create on resource arn:aws:s3:::....

19

just found this PDF on wasabi support portal on how to use rclone

slightly differs from what we are both doing here

20

all i know is that way i do it works, have many TB at wasabi for a couple of years.

you have to post the command and config, as i cannot see into your screen.

that .pdf is from 2017