AWS Compatible -- Anyone using Scaleway?

Seafile Server
1

Hi
Is anyone using Scaleway as the S3 compatible AWS?

I’ve used it on other project and it works well, however I am struggling with Seafile. I have been at it for hours.

I’ve had various errors, but manged to get past them. I can now create a Library however when I try to upload a file I get “internal error” on the upload status dialog.

Looking at the seafile.log:

Authorization: AWS <removed for security>=
2024-03-22 16:24:27 ../common/obj-backend-s3.c(355): Put object fe5d7d278f9859a592f1a9424d64fa8a5e03c171 error 404. Response:
<?xml version='1.0' encoding='UTF-8'?>
<Error><Code>NoSuchBucket</Code><Message>The specified bucket does not exist.</Message><RequestId>txc2b4814eecdf47b0974a6-0065fdb0bb</Reques
tId><BucketName>seafile-sfo</BucketName></Error>
N%
2024-03-22 16:24:27 ../common/fs-mgr.c(878): Failed to write seafile for /opt/seafile/seafile-data/httptemp/cluster-shared/svgA8423959533593
923.pngRKNOK2.

I’ve checked the bucket names and they are correct. If I change the name to test it, I get an error so i am confident the bucket names are correct.

If I remove all the AWS settings, Seafile works – so I know the base setup is good.

Anyone have a suggestion, or a working .conf for Scaleway?

thanks

EDIT: Sorry, should have added it is V 11.0.5 on a Ubuntu server

2

Searching the forum and I see tons of questions about S3 but nothing I am seeing is helping. Lots of unanswered too. Do people generally not use S3?

3

The S3 interface is working well in general, as many customers including ourself use it with S3 compatible storage. But we haven’t tested with Scaleway storage yet.

Different providers have some small differences in their S3 compatible storage interface, which may causing problems.

1 Like
4

You can post your S3 related configurations in seafile.conf here. There may be some misconfiguration. Recently we fixed a few incompatibilities with 3rd-party S3 providers. It works with more providers now, such as BlackBlade, Wasabi, etc.

1 Like
5

Thanks @daniel.pan and @Jonathan for your replies. I slept on my problem overnight and had another attempt today. I wiped the server and started again. This time, despite using exactly the same settings (I think) it worked first time with my S3 provider. This made me very happy.

Uploads of small files are quite slow, but a larger file (say 10MB) seems to upload in good time.

Below I have posted a section of my seafile.conf file, for other to reference, in the hope it helps.

I’m using Scaleway S3 Object Storage, with Private Visibility. Region is Par (Paris)

[commit_object_backend]
name = s3
host = s3.fr-par.scw.cloud
bucket = my-commit-bucketname
key_id = XXXXXXXXXXXXXXXXX
key = 00000000-0000-0000-0000-0000000000
use_https = true

[fs_object_backend]
name = s3
host = s3.fr-par.scw.cloud
bucket = my-object-bucketname
key_id = XXXXXXXXXXXXXXXXX
key = 00000000-0000-0000-0000-0000000000
use_https = true

[block_backend]
name = s3
host = s3.fr-par.scw.cloud
bucket = my-block-bucketname
key_id = XXXXXXXXXXXXXXXXX
key = 00000000-0000-0000-0000-0000000000
use_https = true

I have a memcache issue, but will post that in new thread.