Hello, Anyone can help me? I, [2025-02-24T17:35:41.516926 #1] INFO -- : Terminating async processes I, [2025-02-24T17:35:41.516987 #1] INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/15/bin/…

FWIW, it looks like Digital Ocean has no trouble deleting backups nor expiring missing assets. For providers that are broken, it’d take a long time before unneeded assets caused much of a problem. Keeping a whole bunch of backups including a huge database and all uploads, could be quite a problem …

Hi - I’m Pat Patterson, Chief Technical Evangelist at Backblaze; I arrived on this thread because I have a self-hosted proof-of-concept Discourse forum, and I happened to bump into this exact issue today while configuring my forum to use Backblaze B2 for backups and uploads. Setting AWS_REQUEST_CHE…

[이미지] metadaddy: I’m Pat Patterson, Chief Technical Evangelist at Backblaze thanks for posting!

[이미지] metadaddy: but it’s helpful to know that it doesn’t cover a number of scenarios, including: Deleting files - Discourse is using the DeleteObjects S3 operation to delete multiple files in a single API call, as it should. Yeah, and AWS SDK maintainers are only giving us the cold shoulde…

I’m glad to see that the B2 team has also noticed this issue. Here’s my temporary solution: I commented out all the configurations related to S3 in app.yml and successfully rebuilt Discourse. This does not affect access to previously uploaded files on my site, and any attachments uploaded during t…

[이미지] Yt.w: btw, I still wondering, why not add an option to keep the assets on the Discourse core server (I mean, without storing them on S3? ??? That is how Discourse works out of the box, you need to opt-in explicitly with shipping assets to an object storage service.

I mean, it might be good to have an option to keep Discourse core assets (JS, CSS, etc.) on the local server. At the same time, only user-uploaded files would be stored in S3

You can do that by not enabling “use_s3”, but they are small, I’d just push them and not worry about the wasted space.

Please help me understand correctly. Do you mean to set DISCOURSE_USE_S3: false in app.yml? I would like to do this because my Discourse server is in Asia, and B2 only has servers in the US. Also, this time, the AWS SDK issue is related to asset management, right? So if I store assets on the loc…

The issue is related to removing assets from S3. If you’ll remove just the line that tries to remove the unused assets it will work right now. And it sounds like soon the problem will be resolved. This is the easiest solution. It’s what I recommend. That’s my best free answer.

AWS SDK gem 버전 상승 및 새로운 AWS 데이터 무결성 보호 기능으로 인해 재빌드 불가

지원 자체 호스팅

Falco (Falco) 2월 26, 2025, 1:44오후 32

???

Discourse는 기본적으로 그렇게 작동합니다. 에셋을 오브젝트 저장소 서비스로 전송하려면 명시적으로 선택(opt-in)해야 합니다.

글		댓글	조회수
Error Upgrading from 3.4.0.beta4-dev to 3.5.0.beta1 Support	2	220	3월 6, 2025
Configure an S3 compatible object storage provider for uploads Self-Hosting cdn , configuring , how-to , reference	266	50897	8월 15, 2026
Rake uploads:migrate_to_s3 error Self-hosting s3	8	908	1월 6, 2020
Cannot upload or backup to Amazon S3 Self-hosting backups , s3	3	2198	10월 14, 2015
Issues with AWS CDN and S3 Self-hosting cdn , s3	22	871	12월 30, 2025

AWS SDK gem 버전 상승 및 새로운 AWS 데이터 무결성 보호 기능으로 인해 재빌드 불가

Related topics