I got this error on a recent bootstrap. I’m using Digital Ocean in SFO3. "Tasks: TOP => s3:upload_assets => s3:ensure_cors_rules", "(See full trace by running task with --trace)", "I, [2021-12-16T21:19:05.748497 #1] INFO -- : Installing CORS rules...", "Attempting to apply ASSETS S3 CORS ruleset …

Looks like we should recommend DISCOURSE_S3_INSTALL_CORS_RULE: false for DO like we already do for GCP and BackBlaze in Using Object Storage for Uploads (S3 & Clones) :thinking:

Hello, Sorry for revive this topic but I think I had a related issue few days ago. My setup: Digital Ocean Spaces with s3:upload_assets and s3:expire_missing_assets. CDN - Bunny It seems every rebuild or admin update when it upload assets generate a new CORS rule. It is actually duplicate the o…

[图片] Don: Adding this line will stop generate duplicated CORS rules? Thank you :slightly_smiling_face: I updated the other topic so hopefully it won’t happen to users in the future! Thanks for pointing this out.

Digital Ocean Spaces/S3 的奇怪行为以及 `example.com` 大量重复的 CORS 规则

支持安装

Falco (Falco) 2021 年12 月 16 日 22:24 2

看起来我们应该像在使用对象存储进行上传（S3 和克隆）中为 GCP 和 BackBlaze 所做的那样，为 DO 推荐 DISCOURSE_S3_INSTALL_CORS_RULE: false

话题		回复	浏览量
Digital Ocean Spaces don’t implement the AWS S3 API for the CORS rule Self-hosting s3 , cdn	17	3563	2020 年4 月 30 日
Uppy S3 multipart direct upload to DigitalOcean Spaces Support	2	956	2022 年8 月 23 日
Digital Ocean Spaces (S3) "unable to sign request without credentials set" Support backups , s3 , uploads	20	249	2026 年1 月 7 日
Can't enable Uploads in Digital Ocean Spaces Support	4	1569	2019 年7 月 6 日
SSL_connect returned=1 errno=0 peeraddr=162.243.189.2:443 state=error: certificate verify failed (Hostname mismatch) Self-hosting s3	19	4483	2024 年1 月 9 日

Digital Ocean Spaces/S3 的奇怪行为以及 `example.com` 大量重复的 CORS 规则

相关话题