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/…

[Bild] 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.

Thank you, that’s very helpful for me!

[Bild] Falco: [Bild] 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 …

[Bild] Yt.w: B2 only has servers in the US Not that it particularly helps if you’re in Asia, but, for the record, we also have data centers in Europe (Amsterdam, Netherlands) and, since the beginning of this year, Canada (Toronto). I can’t make any promises, but we are definitely considering…

You’re right! Backblaze does not support x-amz-checksum-crc32, and Discourse’s newer AWS SDK version may have enabled this by default. so i went into the app: ./launcher enter app and uninstalled the current version of AWS SDK: gem uninstall aws-sdk-s3 aws-sdk-core aws-sdk-kms and installe…

[Bild] AntiMetaman: I rebuilt the app and it worked! If you rebuilt the app then the changes made in the container are gone. Perhaps the backblaze folks fixed things while you were doing that.

Kann nicht neu aufbauen wegen AWS SDK Gem-Update und neuen AWS Data Integrity Protections

Unterstützung Installation

Yt.w 26. Februar 2025 um 16:03 37

Danke, das ist sehr hilfreich für mich!

Thema		Antworten	Aufrufe
Error Upgrading from 3.4.0.beta4-dev to 3.5.0.beta1 Support	2	177	6. März 2025
Configure an S3 compatible object storage provider for uploads Self-Hosting cdn , configuring , how-to , reference	265	48641	2. Juli 2026
Rake uploads:migrate_to_s3 error Self-hosting s3	8	870	6. Januar 2020
Cannot upload or backup to Amazon S3 Self-hosting backups , s3	3	2175	14. Oktober 2015
Issues with AWS CDN and S3 Self-hosting cdn , s3	22	566	30. Dezember 2025

Kann nicht neu aufbauen wegen AWS SDK Gem-Update und neuen AWS Data Integrity Protections

Verwandte Themen