I have a bucket set but it seems to be trying to use default? I use GarageHQ as a lightweight MinIO alternative. I’m on 3.6.0.beta1-dev ( ed6beea336 ) [2025-09-14 10:40:34] Removing tmp ‘/var/www/discourse/tmp/backups/default/2025-09-14-104012’ directory… [2025-09-14 10:40:34] Uploading archi…

Yeah. AWS broke the S3 library for lots of other services. Can't rebuild due to AWS SDK gem bump and new AWS Data Integrity Protections has some work-arounds. I created this aws-revert-template.yml to revert to an older version. I don’t know if it works anymore; my file is dated 2025-08-06T05:00:0…

Hmm, i’m not fully convinced the is the problem though [image] unless i’m mistaken i was on 3.6 for longer than 2 days, and yet i got a backup 2 days and 10 days ago.

[imagen] Fma965: unless i’m mistaken i was on 3.6 for longer than 2 days Not much more. I’m thinking that you’re mistaken. Here’s the commit you’re on: UX: control event display through a site setting (#34795) · discourse/discourse@ed6beea · GitHub [image] But also: [imagen] Fma965: …

yes I’m on the commit now, I wasn’t initially when I posted this issue, I updated to rule out a bug, I was on 3.5 when I posted this issue

[imagen] pfaffman: your bucket named “default”? no, as stated in the OP this is why I don’t believe it’s the same issue you are referring to, my bucket is specified , ive tried both in the UI settings of the backup section and via env vars in the yaml, it still tries to use default regardless …

perhaps someone with actual S3 could check to see if it’s correctly selecting a bucket? same for some other 3rd parties like backblaze, r2 etc?

So i created a bucket named “default” and it works as intended, so yes, it’s not correctly picking the bucket name i tell it. [image] So this seems like a bug in Discourse.

[imagen] Fma965: So this seems like a bug in Discourse. Except thousands of people and CDCK hosting would also likely be affected and they are not. It’s much more likely that you deleted or added a character to a line in your app.yml. You can do stuff like this: grep -i S3 /var/discourse/co…

nothing is wrong with my setup nothing was changed except the discourse update. Ive tried configuration in the yaml and configuration in the UI, the UI settings literally show it as “cyanlabs-community” and yet the backup still tries to save to “default” [Screenshot_2025-09-18-21-47-29-55_3aea4af5…

[imagen] Fma965: EXCEPTION: Bucket not found: default This though means the bucket is not there, can you try creating a brand new bucket and creds and see if uploading there works?

S3 (no AWS) dejó de funcionar aleatoriamente, presumiblemente desde una actualización

Soporte

sam (Sam Saffron) 22 Septiembre, 2025 00:23 11

Esto, sin embargo, significa que el bucket no existe. ¿Puedes intentar crear un bucket y credenciales completamente nuevos y ver si la carga allí funciona?

Tema		Respuestas	Vistas
Unable to backup or navigate to backups Bug s3	23	361	18 Noviembre 2024
Issues backing up to s3 Self-hosting backups , s3	5	994	9 Enero 2024
Trouble with Google Bucket for backup Self-hosting backups	6	1267	14 Diciembre 2023
Launcher rebuild fails if s3 settings aren't correct Bug	19	4307	6 Noviembre 2017
Backups to two different S3 regions no longer work Support	7	717	22 Febrero 2022

S3 (no AWS) dejó de funcionar aleatoriamente, presumiblemente desde una actualización

Temas relacionados