A user reports that S3 backups in Discourse (version 3.6.0.beta1-dev) stopped working, with errors indicating the system attempts to use a non-existent “default” bucket instead of the configured one (e.g., “cyanlabs-community”). Despite correct configuration via both UI and environment variables, the backup process fails to use the specified bucket, though the S3 endpoint URL is correctly resolved. The user confirms the issue persists even after creating a “default” bucket, which allows backups to succeed, suggesting a bug in bucket selection. Other users suggest possible misconfiguration or issues with the AWS SDK update, but the user insists their setup is unchanged and correct. The issue appears isolated, as no widespread reports exist, and the user ultimately plans to use the default bucket as a workaround. Fma965, pfaffman, sam, tobiaseigen
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
to clarify nothing has changed on the discourse or garage end since it stopped working except for an update to 3.5 and then to 3.6
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.
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”
Thanks but I feel like i am going around in circles here.
the bucket default did not exist at the start of this conversation, i have since created it and it uses that bucket despite having the bucket cyanlabs-community set in the settings.
both cyanlabs-community and default exist in the s3 instance, but Discourse will not use cyanlabs-community no matter what i try
Whats interesting is it still attempts to make the connection at bucketname.s3.domain.tld, e.g cyanlabsdiscourse.s3.domain.tld as without adding a DNS record it wouldn’t work at that sub sub domain. so the setting is being honoured for the url but it seems to be ignored by the bucket selection
AWS can be mysterious! Sorry you were not able to get your preferred bucket name working. Hard to help without being able to replicate it, so I guess you will have to live with using default as the bucket name.
