Unable to connect to MiniO Server by using v4 signature

Troubleshooting
1

For feature requests, please see: http://www.mattermost.org/feature-requests/.

For troubleshooting questions, please post in the following format:

Summary

Unable to connect to MiniO, S3 compatible storage, by using AWS v4 signature

Steps to reproduce

  1. set AmazonS3SignV2 to false (of course, I know it is default).
  2. change storage to Amazon S3 and set endpoint and credentials.
  3. Click ‘Test Connection’
  4. show ‘Connection unsuccessful: Error checking if bucket exists. - undefined’
  5. If set AmazonS3SignV2 to true, the connection will establish successfully.

Expected behavior

Successful.

Observed behavior

What did you see happen? Please include relevant error messages and/or screenshots.

Log


Apr 14 04:12:39 v13 mattermost[2497]: HEAD /chatter/ HTTP/1.1

Apr 14 04:12:39 v13 mattermost[2497]: Host: s3.leafia.org

Apr 14 04:12:39 v13 mattermost[2497]: User-Agent: Minio (linux; amd64) minio-go/v6.0.14

Apr 14 04:12:39 v13 mattermost[2497]: Authorization: AWS4-HMAC-SHA256 Credential=**REDACTED**/20190414/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=**REDACTED**

Apr 14 04:12:39 v13 mattermost[2497]: X-Amz-Content-Sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

Apr 14 04:12:39 v13 mattermost[2497]: X-Amz-Date: 20190414T111239Z

Apr 14 04:12:39 v13 mattermost[2497]: #015

Apr 14 04:12:39 v13 mattermost[2497]: HTTP/1.1 403 Forbidden

Apr 14 04:12:39 v13 mattermost[2497]: Connection: close

Apr 14 04:12:39 v13 mattermost[2497]: Accept-Ranges: bytes

Apr 14 04:12:39 v13 mattermost[2497]: Content-Security-Policy: block-all-mixed-content

Apr 14 04:12:39 v13 mattermost[2497]: Date: Sun, 14 Apr 2019 11:12:39 GMT

Apr 14 04:12:39 v13 mattermost[2497]: Server: Minio/RELEASE.2019-04-09T01-22-30Z

Apr 14 04:12:39 v13 mattermost[2497]: Strict-Transport-Security: max-age=15552000; includeSubdomains;

Apr 14 04:12:39 v13 mattermost[2497]: Vary: Origin

Apr 14 04:12:39 v13 mattermost[2497]: X-Amz-Request-Id: 159552DE08BEF9DE

Apr 14 04:12:39 v13 mattermost[2497]: X-Content-Type-Options: nosniff

Apr 14 04:12:39 v13 mattermost[2497]: X-Frame-Options: SAMEORIGIN

Apr 14 04:12:39 v13 mattermost[2497]: X-Minio-Deployment-Id: 71e60e4f-556c-4858-bdc6-6cda5d5801fb

Apr 14 04:12:39 v13 mattermost[2497]: X-Xss-Protection: 1; mode=block

Apr 14 04:12:39 v13 mattermost[2497]: ---------END-HTTP---------

Apr 14 04:12:39 v13 mattermost[2497]: {"level":"error","ts":1555240359.9427152,"caller":"web/context.go:52","msg":"Error checking if bucket exists.","path":"/api/v4/file/s3_test","request_id":"o4h5e76anbyzznanmnwkwc4n1h","ip_addr":"203.141.134.112","user_id":"hjgxkhqkjpn3pmouoakjjfsqww","method":"POST","err_where":"TestFileConnection","http_code":500,"err_details":"Access Denied."}

Versions

Minio

Version: 2019-04-09T01:22:30Z
Release-Tag: RELEASE.2019-04-09T01-22-30Z
Commit-ID: a2e344bf30c7750c0a152f046a70d327f2f5ccf5

Mattermost : mattermost-5.9.0-linux-amd64

p.s.

The MiniO developer says Minio with v4 signature needs path-style access. Is this configurable?