Date error with wasabi

Help and Support
1

Getting this error when I try to do a rclone ls wasabi:
AWS authentication requires a valid Date or x-amz-date header

I've tried it with a root key pair, and I've also reset the config up several times, am using the v4 auth

rclone v1.55.1

MacOS 11.2.3

command

rclone ls wasabi:

config

[wasabi]
type = s3
provider = Wasabi
env_auth = false
access_key_id = xxx
secret_access_key = xxx
region =
endpoint = s3.eu-central-1.wasabisys.com
location_constraint =
acl =
server_side_encryption =
storage_class =

A log from the command with the -vv flag

2021/05/31 21:07:01 DEBUG : Using config file from "/Users/me/.config/rclone/rclone.conf"
2021/05/31 21:07:01 DEBUG : rclone: Version "v1.55.1" starting with parameters ["./rclone" "ls" "wasabi:" "-vv"]
2021/05/31 21:07:01 DEBUG : Creating backend with remote "wasabi:"
2021/05/31 21:07:03 DEBUG : 6 go routines active
2021/05/31 21:07:03 Failed to ls: AccessDenied: Access Denied
	status code: 403, request id: BE8F95F4D19BC045, host id: z9r/uhWd2T4kYHXb4hwBmJ5VCupuvx05/5ib+3b2ZOLL1KxsKbV3m+h/ev17DstqkHNnWRT//c0e

rclone -vv --dump bodies lsd wasabi:

2021/05/31 21:09:55 DEBUG : Using config file from "/Users/me/.config/rclone/rclone.conf"
2021/05/31 21:09:55 DEBUG : rclone: Version "v1.55.1" starting with parameters ["/Users/me/rclone" "-vv" "--dump" "bodies" "lsd" "wasabi:"]
2021/05/31 21:09:55 DEBUG : Creating backend with remote "wasabi:"
2021/05/31 21:09:55 DEBUG : You have specified to dump information. Please be noted that the Accept-Encoding as shown may not be correct in the request and the response may not show Content-Encoding if the go standard libraries auto gzip encoding was in effect. In this case the body of the request will be gunzipped before showing it.
2021/05/31 21:09:55 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2021/05/31 21:09:55 DEBUG : HTTP REQUEST (req 0xc0005d6200)
2021/05/31 21:09:55 DEBUG : GET / HTTP/1.1
Host: s3.eu-central-1.wasabisys.com
User-Agent: rclone/v1.55.1
Authorization: XXXX
X-Amz-Content-Sha256: xxx
X-Amz-Date: 20210531T200955Z
Accept-Encoding: gzip

2021/05/31 21:09:55 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2021/05/31 21:09:55 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2021/05/31 21:09:55 DEBUG : HTTP RESPONSE (req 0xc0005d6200)
2021/05/31 21:09:55 DEBUG : HTTP/1.1 200 OK
Transfer-Encoding: chunked
Content-Type: application/xml
Date: Mon, 31 May 2021 20:09:55 GMT
Server: WasabiS3/6.2.4752-2021-05-15-1e0f09e (head03)
X-Amz-Id-2: xxxx
X-Amz-Request-Id: xxxx

172
<?xml version="1.0" encoding="UTF-8"?>
<ListAllMyBucketsResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Owner><ID>51F99E860A0A2009D4BD5701C0FBAD8AB215132BDF723B9AA42AFDB9ED0E608E</ID><DisplayName>me</DisplayName></Owner><Buckets><Bucket><Name>mybucketxxx</Name><CreationDate>2021-05-31T11:15:07.000Z</CreationDate></Bucket></Buckets></ListAllMyBucketsResult>
0

2021/05/31 21:09:55 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
          -1 2021-05-31 12:15:07        -1 redio
2021/05/31 21:09:55 DEBUG : 6 go routines active
2

hello and welcome to the forum,

i use wasabi, have over 20 remotes, never got that error.

do you have any s3 polices in use?

3

do you have any s3 polices in use?

Yes :man_facepalming: I had a blanket bucket policy I'd forgotten about (for unauthenticated users) which was affecting it. Have added an exception and it's fine now. Thanks for the suggestion!

4

yeah, access denied are usually s3 policy issues.
glad we got it worked out quickly!

i thought that since the rclone lsd did not error and the rclone ls did

1 Like
5

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.