Hello, I am using Seafile Pro with Docker Compose. I have successfully gotten Seafile to use S3-compatible object storage buckets for the fs and commits storage backends, but I can’t seem to get the objects to work with S3. I also get an elastic search error 137. My goal is to us my S3 provider for as much as possible because S3 storage is much cheaper than virtual private server block storage. When I test with a ~2 gigabyte Linux ISO, it ends up with nothing in the blocks bucket and space taken up on my VPS host instead.
Any advice on how to fix this or why this is happening appreciated.
Here is my seafile.conf:
[database]
type = mysql
host = db
port = 3306
user = seafile
password = aaaa
db_name = seafile_db
connection_charset = utf8
[commit_object_backend]
name = s3
bucket = dddd
key_id = eeee
key = ffff
host = gggg
path_style_request = false
use-sigv4 = True
memcached_options = --SERVER=localhost --POOL-MIN=10 --POOL-MAX=100
[fs_object_backend]
name = s3
bucket = qqqq
key_id = rrrr
key = ssss
host = tttt
host = uuuu
path_style_request = false
use-sigv4 = True
memcached_options = --SERVER=localhost --POOL-MIN=10 --POOL-MAX=100
[block_object_backend]
name = s3
bucket = wwww
key_id = xxxxx
key = yyyyy
host = zzzzz
path_style_request = false
use-sigv4 = True
memcached_options = --SERVER=localhost --POOL-MIN=10 --POOL-MAX=100