Skip to content

Using restic backup to minio-sia causes a signature mismatch to occur. #1

@mannp

Description

@mannp

Following the restic to minio setup -> https://docs.minio.io/docs/restic-with-minio

I create a bucket on minio-sia, which is fine

I then try to initialise a repository on that server and it fails with;

restic init
create backend at s3:http://192.168.1.99:9001/restic failed: client.BucketExists: The request signature we calculated does not match the signature you provided. Check your key and signing method.

This is the log from the docker;

time="2017-08-30T21:17:14+01:00 level=error msg="{"method":"GET","reqURI":"/restic/?location=","header":{"Accept-Encoding":["gzip"],"Authorization":["AWS4-HMAC-SHA256 Credential=/20170830/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=f61e152f554c826148b8285cb19f9a051e3b05d124c45680d988a83e7998922b"],"Host":["192.168.1.99:9001"],"User-Agent":["Minio (darwin; amd64) minio-go/3.0.0"],"X-Amz-Content-Sha256":["e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"],"X-Amz-Date":["20170830T201714Z"]}}" cause="Signature does not match" source="[gateway-handlers.go:907:gatewayAPIHandlers.GetBucketLocationHandler()]"

Executing the same command on a locally created minio instance on a mac allows the repository to be initialised and backups to occur successfully.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions