I tried to use Oracle Cloud Infrastructure Object Storage, which has Amazon S3 Compatibility API, as the backend.
I configured seafile.conf like:
[commit_object_backend]
name = s3
bucket = my-commit-objects
key_id = ***
key = ***
host = ***.compat.objectstorage.ap-tokyo-1.oraclecloud.com
path_style_request = true
use_https = true
use_v4_signature = true
aws_region = ap-tokyo-1
and fs_object_backend/block_backend likewise, and I got error like:
2023-10-23 17:59:55 …/common/s3-client.c(949): S3 error status for HEAD: 403.
<?xml version="1.0" encoding="UTF-8"?>< Error>Header date must be signed< Code>AccessDenied< /Code>< /Error>
2023-10-23 17:59:55 …/common/s3-client.c(725): S3 error status for PUT: 403.
2023-10-23 17:59:55 …/common/s3-client.c(726): Request URL: https://***.compat.objectstorage.ap-tokyo-1.oraclecloud.com/my-commit-objects/***/***
2023-10-23 17:59:55 …/common/s3-client.c(727): Request headers:
2023-10-23 17:59:55 …/common/s3-client.c(624): Date: Mon, 23 Oct 2023 08:59:55 +0000
2023-10-23 17:59:55 …/common/s3-client.c(624): Authorization: AWS4-HMAC-SHA256 Credential=***/20231023/ap-tokyo-1/s3/aws4_request,SignedHeaders=host;x-amz-content-sha256,Signature=***
2023-10-23 17:59:55 …/common/s3-client.c(624): x-amz-content-sha256: ***
2023-10-23 17:59:55 …/common/obj-backend-s3.c(348): Put object *** error 403. Response:2023-10-23 17:59:55 repo-mgr.c(7176): Failed to add commit.
Any suggestion for the situation?