Seafile V13 could not resolve self-hosted s3 server host name

Seafile Server Docker
1

Hey,

I’m trying to self host the seafile V13 with s3 as the backend storage. But I have 3 different buckets from different servers, the block bucket is from a online provider with s3 compatible api, then buckets fs and commit are self hosted directly on my machine with minio and behind a caddy proxy.

Problem is that I can manage the minio instance from other s3 clients with no issue, but when I configured it in the seafile.conf and started the server, it came with this error:

[2025-11-10 15:44:40] [WARNING] ../common/s3-client.c(1346): [S3] libcurl failed to head seafile-commit:3be63b07-da86-41ec-812c-97c4dc459e66/f2aafe6da453b94edeec2b3c7bcad9c84f98965c: Couldn't resolve host name.
[2025-11-10 15:44:40] [WARNING] ../common/s3-client.c(1346): [S3] libcurl failed to head seafile-commit:3be63b07-da86-41ec-812c-97c4dc459e66/f2aafe6da453b94edeec2b3c7bcad9c84f98965c: Couldn't resolve host name.
[2025-11-10 15:44:40] [WARNING] ../common/s3-client.c(1346): [S3] libcurl failed to head seafile-commit:3be63b07-da86-41ec-812c-97c4dc459e66/f2aafe6da453b94edeec2b3c7bcad9c84f98965c: Couldn't resolve host name.
[2025-11-10 15:44:40] [WARNING] ../common/s3-client.c(1091): [S3] libcurl failed to put seafile-commit:3be63b07-da86-41ec-812c-97c4dc459e66/f2aafe6da453b94edeec2b3c7bcad9c84f98965c: Couldn't resolve host name.
[2025-11-10 15:44:40] [WARNING] ../common/s3-client.c(1091): [S3] libcurl failed to put seafile-commit:3be63b07-da86-41ec-812c-97c4dc459e66/f2aafe6da453b94edeec2b3c7bcad9c84f98965c: Couldn't resolve host name.
[2025-11-10 15:44:40] [WARNING] ../common/s3-client.c(1091): [S3] libcurl failed to put seafile-commit:3be63b07-da86-41ec-812c-97c4dc459e66/f2aafe6da453b94edeec2b3c7bcad9c84f98965c: Couldn't resolve host name.

but I have tried curl and ping my s3 server from the container, and they all worked fine, only seafile couldn’t resolve the host name.

Here is my seafile.conf:

[fileserver]
port=8082

[commit_object_backend]
name = s3
bucket = seafile-commit
key_id = 
key = 
host = https://s3.itzdrli.cc
path_style_request = true
use_v4_signature = true
use_https = true

[fs_object_backend]
name = s3
bucket = seafile-fs
key_id = 
key = 
host = https://s3.itzdrli.cc
path_style_request = true
use_v4_signature = true
use_https = true

[block_backend]
name = s3
bucket = bucket-482-981
key_id = 
key = 
aws_region = 
host = 
path_style_request = true
use_v4_signature = true
use_https = true

did I configure something wrong? would be appreciated if someone could help me on this, thanks

2

Hello @itzdrli ,

You can change the host to s3.itzdrli.cc and try again. The https prefix doesn’t need to be specified.

3

In version 13.0, we recommend to set S3 buckets in .env file as in the installation document. S3 Backend - Seafile Admin Manual

You can try whether put the S3 configurations to .env file can solve your problem.

4

Thanks, I’m aware of this. But since I have 3 buckets different and I cloud not find env variables from the manual, so I went with the conf