Trying to setup Digital Ocean Spaces for S3 storage. I get this when I try to run backups… [image] Same when I upload photos… [image] I have this setup… [image] …but I’m not sure how to test if those actually work. I don’t know these systems very well. This is just for a small friends group forum. Initially I had the below live, but I had to comment it back out on the app.yml because it wouldn’t rebuild with those lines live. Not sure if it’s still necessary or not at this point… [Bild]Configure an S3 compatible object storage provider for uploads after_assets_precompile: - exec: cd: $home cmd: - sudo -E -u discourse bundle exec rake s3:upload_assets - sudo -E -u discourse bundle exec rake s3:expire_missing_assets I’ve manually uploaded a file from the Digital Ocean Spaces admin area, set it to public, and I’m able to pull it up through a browser. [image] I also manually created the “*****-backups” folder in DO Spaces. [image] Here’s an example of how little I know. I’m stuck here and I don’t really know why. Somehow I’ve backed myself out of something and I’m not sure how to get back. [image] For some reason what’s usually in /var/discourse now seems to be in /var/www/discourse I’m just stuck at this point though. I’ve searched through the forum and not found anything that will solve it. I’ve spent a day in the same loop. This is along the same lines, but it’s actual AWS S3 and not DO Spaces (S3)… [Bild] AWS S3 upload - unable to sign request without credentials set Support Tried now, to set up IAM User with credentials and give it s3:* permissions, and now the upload works, but discourse can´t display it afterwards: [The image failed to load, resulting in a black screen with the text "The image could not be loaded." displayed. (Captioned by AI)] As I´m working in a company, and there are SCP (Service control policies) active for our accounts, it seems that public access is generally blocked [The image shows a settings page where public access is blocked for a… Any assistance would be appreciated. Thank you.

This is what finally worked: These settings had to be in the app.yml config in order for it to finally run the rakes correctly. When they were just in the /admin/site_settings/ area, it wouldn’t run the rakes correctly. I was getting an errror: ERROR: Ensure S3 is configured in config/discourse.conf or environment vars The settings are from here… Configure an S3 compatible object storage provider for uploads Specifically, I used non-custom Spaces settings with two spaces before each line. … DISCOURSE_USE_S3: true DISCOURSE_S3_REGION: whatever DISCOURSE_S3_ENDPOINT: https://nyc3.digitaloceanspaces.com DISCOURSE_S3_ACCESS_KEY_ID: myaccesskey DISCOURSE_S3_SECRET_ACCESS_KEY: mysecretkey DISCOURSE_S3_CDN_URL: https://nyc3.cdn.digitaloceanspaces.com DISCOURSE_S3_BUCKET: my-files DISCOURSE_S3_BACKUP_BUCKET: my-files/my-backups DISCOURSE_BACKUP_LOCATION: s3 DISCOURSE_S3_INSTALL_CORS_RULE: false NOTE: DISCOURSE_S3_REGION should literally say “whatever” and not something that could be construed as an actual S3 region (ie. us-west-1). [image] Also these settings, in the hooks section of the ## Plugins go here area… after_assets_precompile: - exec: cd: $home cmd: - sudo -E -u discourse bundle exec rake s3:upload_assets - sudo -E -u discourse bundle exec rake s3:expire_missing_assets This is where I ran into an issue last time. Once that’s in place and I rebuilt, I was getting this loading screen when I tried to bring up our forum in a browser. [image] This is only because it’s looking for assets that haven’t yet been updated. This is where it’s time to run the rakes, from inside the app… ./launcher enter app rake s3:upload_assets Once that ran, the items number jumped up and an “assets” folder showed up in our bucket… [image] Then the forum started loading correctly. These are the only S3 related settings that I have showing in my /admin/site-settings area… [image] I ran this to upload all of the files and it updated the URLs from the old path to the new (non-CDN). rake uploads:migrate_to_s3 --trace [image] The items number more than tripled after that finished. The only thing I noticed was that old post image paths were using the S3 ENDPOINT URL versus newly posted images were using the S3 CDN URL. https:/my-storage.sfo3.digitaloceanspaces.com/ vs https:/my-storage.sfo3.cdn.digitaloceanspaces.com/ I didn’t really care because at least it was all using S3. But I tried running… rake posts:rebake [image] It killed it because it ran out of memory. I tried running this instead… rake posts:rebake_uncooked_posts It ran out of memory a few times and restarted itself, then ran out of memory again. Ran it again. Eventually it got through cooking them all. [image] Once it ran all the way through to 100%, all of the links were finally using the S3 CDN URL path, old and new posts. Over 34062 items at 65.9 GB of storage (a backup is <9 GB). Really happy that it’s all working off of S3 now, including backups. Speaking of, probably a good time to run one! Hope this helps someone. Good luck!

Digital Ocean Spaces (S3) „Anfrage kann nicht ohne gesetzte Anmeldeinformationen signiert werden“

Produktunterstützung

Thema		Antworten	Aufrufe
Migrate_to_s3 for Digital Ocean Spaces woes Self-hosting s3	25	3611	28. März 2019
Configure an S3 compatible object storage provider for uploads Self-Hosting cdn , configuring , how-to , reference	267	54785	15. September 2026
Issues with AWS CDN and S3 Self-hosting cdn , s3	22	1366	30. Dezember 2025
Digital Ocean Spaces don’t implement the AWS S3 API for the CORS rule Self-hosting cdn , s3	16	3822	22. April 2020
Set up file and image uploads to S3 Self-Hosting configuring , how-to	35	122333	25. Oktober 2025

Digital Ocean Spaces (S3) „Anfrage kann nicht ohne gesetzte Anmeldeinformationen signiert werden“

Verwandte Themen