Error: valid Date or x-amz-date header with S3 / wasabi

Help and Support
1

Hey guys, connecting to S3 clone Wasabi I'm getting the follow error:

ERROR : : error reading destination directory: AccessDenied: AWS authentication requires a valid Date or x-amz-date header

researching here I don't see any mention of it. Google says mostly Java related things but that's out of league.
I've checked and double checked keys and recreated remote.

Can anyone shed some light on this?

NOTE: it works with AWS S3

2

That sounds like the authentication is off somehow..

Can you post the result of rclone -vv --dump bodies lsd wasabi:

Also check the time on your computer is correct.

3

Hey ncw,

time is correct, I synced with servers and also set tz to UTC.

here's bodies dump. Removed identifying info

2019/05/13 15:40:16 DEBUG : rclone: Version "v1.47.0" starting with parameters ["rclone" "-vv" "--dump" "bodies" "lsd" "WasabI:"]
2019/05/13 15:40:16 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2019/05/13 15:40:16 DEBUG : Using v2 auth
2019/05/13 15:40:16 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2019/05/13 15:40:16 DEBUG : HTTP REQUEST (req 0xc000388000)
2019/05/13 15:40:16 DEBUG : GET / HTTP/1.1
Host: s3.us-west-1.wasabisys.com
User-Agent: rclone/v1.47.0
Authorization: XXXX
Date: Mon, 13 May 2019 19:40:16 UTC
Accept-Encoding: gzip

2019/05/13 15:40:16 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2019/05/13 15:40:17 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2019/05/13 15:40:17 DEBUG : HTTP RESPONSE (req 0xc000388000)
2019/05/13 15:40:17 DEBUG : HTTP/1.1 403 Forbidden
Transfer-Encoding: chunked
Content-Type: application/xml
Date: Mon, 13 May 2019 19:40:22 GMT
Server: WasabiS3/3.4.2643-2019-05-09-3d339a5 (head01)
X-Amz-Id-2: OMIT
X-Amz-Request-Id: OMIT

123

<?xml version="1.0" encoding="UTF-8"?>

AccessDeniedAWS authentication requires a valid Date or x-amz-date headerOMITOMIT
0

2019/05/13 15:40:17 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2019/05/13 15:40:17 ERROR : : error listing: AccessDenied: AWS authentication requires a valid Date or x-amz-date header
status code: 403, request id: OMIT, host id: OMIT
2019/05/13 15:40:17 Failed to lsd: AccessDenied: AWS authentication requires a valid Date or x-amz-date header
status code: 403, request id: OMIT, host id: OMIT

4

That is strange, there really is no X-Amz-Date: 20190513T205322Z in the request. That is what I see when I do the equivalent command

Can you paste the result of rclone config show Wasabi (XXX out the access_key_id and secret_access_key).

I suspect that is the problem, you want to be using v4 auth which is the default.

My wasabi config looks like this

[wasabi]
type = s3
env_auth = false
access_key_id = XXX
secret_access_key = XXX
region = 
endpoint = s3.wasabisys.com
location_constraint = 
acl = 
server_side_encryption = 
storage_class =
5

Thanks ncw. It's working now

I was under the impression that I needed to use the V2 auth. Changed to v4 and smooth sailing

1 Like
6

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