请教一下 Alist S3 如何在思源笔记中配置

折腾了许久，一直报错：同步失败：锁定云端同步目录失败，请稍后再试 (Provider: S3) v3.0.17。

所以请教一下大家。

首先介绍下环境：

• Alist：版本 v3.35.0，docker 部署，采用内网穿透和组网访问。
• 思源笔记：版本 v3.17，docker 部署，采用内网穿透和组网访问。

Alist 已经按照文档设置了对象储存，使用 S3 Browser 通过内网穿透访问正常，可以列出文件，下载文件，上传文件。但是相同配置在思源笔记上，可以读取到储存桶，但是无法进行同步，报错信息：“同步失败：锁定云端同步目录失败，请稍后再试 (Provider: S3) v3.0.17”。

现在也不知道该如何配置了，是不支持 Alist 的对象储存还是配置有问题，求解答。

配置截图：

1、alist 对象储存

2、S3 Browser 配置

3、思源笔记云端配置

思源最近日志：

E 2024/06/20 13:03:15 repository.go:1307: sync data repo failed: lock cloud repo failed
I 2024/06/20 13:03:49 repository.go:1279: syncing data repo [device=14t7gqop6hee, kernel=3bsm7iv, provider=2, mode=a/true]
I 2024/06/20 13:03:49 ref.go:50: got local latest [device=14t7gqop6hee/linux, id=e390a5ecea4536844aa53773e3e3fa29d23dd3c9, files=323, size=58.24 MB, created=2024-06-20 11:29:46]
I 2024/06/20 13:03:49 repo.go:595: walk data [files=323] cost [38.835424ms]
I 2024/06/20 13:03:49 ref.go:50: got local latest [device=14t7gqop6hee/linux, id=e390a5ecea4536844aa53773e3e3fa29d23dd3c9, files=323, size=58.24 MB, created=2024-06-20 11:29:46]
E 2024/06/20 13:03:50 sync_lock.go:159: upload lock sync failed: NoSuchKey: 
	status code: 404, request id: 3353F64E3CF5CA44, host id: MzM1M0Y2NEUzQ0Y1Q0E0NDMzNTNGNjRFM0NGNUNBNDQzMzUzRjY0RTNDRjVDQTQ0MzM1M0Y2NEUzQ0Y1Q0E0NA==
E 2024/06/20 13:03:50 repository.go:1307: sync data repo failed: lock cloud repo failed
E 2024/06/20 13:05:17 sync_lock.go:159: upload lock sync failed: NoSuchKey: 
	status code: 404, request id: 3353F64E3CF5CA48, host id: MzM1M0Y2NEUzQ0Y1Q0E0ODMzNTNGNjRFM0NGNUNBNDgzMzUzRjY0RTNDRjVDQTQ4MzM1M0Y2NEUzQ0Y1Q0E0OA==
I 2024/06/20 13:12:09 repository.go:1279: syncing data repo [device=14t7gqop6hee, kernel=3bsm7iv, provider=2, mode=a/true]
I 2024/06/20 13:12:09 ref.go:50: got local latest [device=14t7gqop6hee/linux, id=e390a5ecea4536844aa53773e3e3fa29d23dd3c9, files=323, size=58.24 MB, created=2024-06-20 11:29:46]
I 2024/06/20 13:12:09 repo.go:595: walk data [files=323] cost [80.742294ms]
I 2024/06/20 13:12:09 ref.go:50: got local latest [device=14t7gqop6hee/linux, id=e390a5ecea4536844aa53773e3e3fa29d23dd3c9, files=323, size=58.24 MB, created=2024-06-20 11:29:46]
E 2024/06/20 13:12:10 sync_lock.go:159: upload lock sync failed: NoSuchKey: 
	status code: 404, request id: 3353F64E3CF5CA4C, host id: MzM1M0Y2NEUzQ0Y1Q0E0QzMzNTNGNjRFM0NGNUNBNEMzMzUzRjY0RTNDRjVDQTRDMzM1M0Y2NEUzQ0Y1Q0E0Qw==
E 2024/06/20 13:12:10 repository.go:1307: sync data repo failed: lock cloud repo failed
I 2024/06/20 13:26:49 repository.go:1279: syncing data repo [device=14t7gqop6hee, kernel=3bsm7iv, provider=2, mode=a/true]
I 2024/06/20 13:26:49 ref.go:50: got local latest [device=14t7gqop6hee/linux, id=e390a5ecea4536844aa53773e3e3fa29d23dd3c9, files=323, size=58.24 MB, created=2024-06-20 11:29:46]
I 2024/06/20 13:26:49 repo.go:595: walk data [files=323] cost [25.780109ms]
I 2024/06/20 13:26:49 ref.go:50: got local latest [device=14t7gqop6hee/linux, id=e390a5ecea4536844aa53773e3e3fa29d23dd3c9, files=323, size=58.24 MB, created=2024-06-20 11:29:46]
E 2024/06/20 13:26:49 sync_lock.go:159: upload lock sync failed: NoSuchKey: 
	status code: 404, request id: 3353F64E3CF5CA51, host id: MzM1M0Y2NEUzQ0Y1Q0E1MTMzNTNGNjRFM0NGNUNBNTEzMzUzRjY0RTNDRjVDQTUxMzM1M0Y2NEUzQ0Y1Q0E1MQ==
E 2024/06/20 13:26:49 repository.go:1307: sync data repo failed: lock cloud repo failed