[图片]Configure an S3 compatible object storage provider for uploads AWS S3 What we officially support and use internally. @Falco I this still the case? I thought I read something about recent issues using AWS but I can’t find the topic again. I am having numerous using AWS S3 using the various relevant topics as guides. Backups are working as expected but using Cloudfront as CDN or uncommenting DISCOURSE_USE_S3 and/or DISCOURSE_S3_BUCKET causes a perpetual throbber to happen. I suspect I have something misconfigured in the uploads bucket and/or the Cloudfront distribution but I have not been able to find a mistake. Both upload and backup buckets are behind the distribution and backups work fine so??? discourse-cdn.repealobbba.org CNAME —> amazonassigned.cloudfront.net DISCOURSE_CDN_URL: https://discourse-cdn.repealobbba.org ## S3 storage config # DISCOURSE_USE_S3: true DISCOURSE_S3_REGION: us-east-1 DISCOURSE_S3_ACCESS_KEY_ID: ACCESS_KEY_ID DISCOURSE_S3_SECRET_ACCESS_KEY: SECRET_ACCESS_KEY DISCOURSE_S3_CDN_URL: amazonassigned.cloudfront.net or # DISCOURSE_S3_BUCKET: repeal-obbba-discuss-uploads DISCOURSE_S3_BACKUP_BUCKET: repeal-obbba-discuss-backups DISCOURSE_BACKUP_LOCATION: s3 Additionally, adding this to config 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 Gives FAILED TO BOOTSTRAP error FAILED -------------------- Pups::ExecError: cd /var/www/discourse && sudo -E -u discourse bundle exec rake s3:upload_assets failed with return # Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.3.0/lib/pups/exec_command.rb:131:in `spawn' exec failed with the params {"cd"=>"$home", "cmd"=>["sudo -E -u discourse bundle exec rake s3:upload_assets", "sudo -E -u discourse bundle exec rake s3:expire_missing_assets"]} bootstrap failed with exit code 1 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. as always… Any thoughts or suggestions would be appreciated.

Whew! It took a ton of time and some hours (8 over 2 calls) on the phone with a very helpful Amazon engineer but I think I have my head around this. Things are working great on the RepealOBBBA site and my process is reproducible to other sites. I may write things up but a few notes for now: DISCOURSE_CDN_URL (if using AWS S3) and DISCOURSE_S3_CDN_URL require their own Cloudfront distributions. DISCOURSE_CDN_URL does not use a bucket. DISCOURSE_CDN_URL can be a nonAWS CDN. Bunny.net works great. (I am told Bunny Storage with S3 support is due out 2026 1st quarter) DISCOURSE_CDN_URL and DISCOURSE_S3_CDN_URL CDNs can be branded urls with the appropriate DNS config. DISCOURSE_S3_CDN_URL requires an uploads bucket. The uploads bucket requires ACLs enabled and “Everyone (public access)” set to “Read” and you must set a policy for the bucket. The backups bucket does not require ACLs or policy. Edit(s) Check the box in S3 use CDN URL for all uploads: Use CDN URL for all the files uploaded to s3 instead of only for images. Not enabling always caused failures for me. [Screenshot 2025-12-20 122637] I imagine many may read the above and go duhhh Phil, no kidding, that is obvious but… my BBS head did not get it right away.

Thanks for continuing… Yes, rake tasks are run, makes no difference. ./launcher enter app rake posts:rebake rake uploads:migrate_to_s3 rake posts:rebake_uncooked_posts Throbber persists. rake uploads:migrate_to_s3 does yield an error Migrating uploads to S3 for 'default'... Some uploads were not migrated to the new scheme. Running the migration, this may take a while... rake aborted! FileStore::ToS3MigrationError: Some uploads could not be migrated to the new scheme. You need to fix this manually. (FileStore::ToS3MigrationError) /var/www/discourse/lib/file_store/to_s3_migration.rb:156:in `migrate_to_s3' /var/www/discourse/lib/file_store/to_s3_migration.rb:59:in `migrate' /var/www/discourse/lib/tasks/uploads.rake:126:in `migrate_to_s3' /var/www/discourse/lib/tasks/uploads.rake:106:in `block in migrate_to_s3_all_sites' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rails_multisite-7.0.0/lib/rails_multisite/connection_management/null_instance.rb:49:in `with_connection' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rails_multisite-7.0.0/lib/rails_multisite/connection_management/null_instance.rb:36:in `each_connection' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rails_multisite-7.0.0/lib/rails_multisite/connection_management.rb:17:in `each_connection' /var/www/discourse/lib/tasks/uploads.rake:104:in `migrate_to_s3_all_sites' /var/www/discourse/lib/tasks/uploads.rake:100:in `block in ' /usr/local/bin/bundle:25:in `load' /usr/local/bin/bundle:25:in ` ' Tasks: TOP => uploads:migrate_to_s3 At least one CDN checker shows discourse-cdn.repealobbba.org -->Amazon CloudFront and console still shows images and js files are being called from the CDN [Screenshot 2025-12-10 192413]

The assets are called from the cdn, but are they there? If not, are they in the bucket? Are they accessible from the bucket? You likely have some uploads in a different bucket or something that keeps them from being in the expected place. If so, you’ll need to fix those by hand like it sats. You’ll need to access the console and see where they are on the upload record. Does the upload assets task seem to be working? The throbber keeps running because the other assets are no loading.

Yes they are there, files are in the bucket as assets Accessible: https://repeal-obbba-discuss-uploads.s3.us-east-1.amazonaws.com/assets/logo-815195ae.png Only two buckets, uploads and backups. Backups are working fine. rake s3:upload_assets gave error: rake aborted! Aws::S3::Errors::AccessControlListNotSupported: The bucket does not allow ACLs (Aws::S3::Errors::AccessControlListNotSupported) Switched to ACLs enabled and ran s3:upload_assets edit: uploads:migrate_to_s3 again but… FileStore::ToS3MigrationError: Some uploads could not be migrated to the new scheme. You need to fix this manually. (FileStore::ToS3MigrationError) ??? You need to fix this manually. (FileStore::ToS3MigrationError)

It sounds like you fixed the bucket and it’s now able to upload assets, so the site should work now. Dealing with the uploads that won’t migrate is another (complicated) issue. Here’s one of the assets you’re trying to serve: https://discourse-cdn.repealobbba.org/assets/start-discourse-6f03a463.br.js The cert is broken, so that’s your problem. There is a cert, but it doesn’t match the URL. As I suggested earlier, look at the network tab of the dev tools in your browser and see this: [image]

edit from above Switched to ACLs enabled and ran s3:upload_assets edit: uploads:migrate_to_s3 again s3:upload_assets completes without issues now I see the network errors. Is the cert an AWS issue? Thanks again for your time on this!!

[图片] philh: I see the network errors. Is the cert an AWS issue? Yes. The cert doesn’t match the host name. It matches *.cloudfront.net This works: https://repeal-obbba-discuss-uploads.s3.us-east-1.amazonaws.com/assets/logo-815195ae.png This does not work: https://discourse-cdn.repealobbba.org/assets/start-discourse-6f03a463.br.js This works: https://repeal-obbba-discuss-uploads.s3.us-east-1.amazonaws.com/assets/start-discourse-6f03a463.br.js So you need to change your s3 CDN to https://repeal-obbba-discuss-uploads.s3.us-east-1.amazonaws.com – oh, I guess that’s the bucket address, so that wouldn’t be ideal, but it would work.

[图片] pfaffman: So you need to change your s3 CDN to https://repeal-obbba-discuss-uploads.s3.us-east-1.amazonaws.com – oh, I guess that’s the bucket address, so that wouldn’t be ideal, but it would work. Not to keen on “so that wouldn’t be ideal” :wink: Looking at AWS Alternate domain names as a possible solution. [Screenshot 2025-12-11 113613] Maybe it is just me but adding a CDN that @Discourse uses internally should maybe not be so difficult and require the kind support from folks like @pfaffman Maybe @Falco or @sam and @team (can’t mention team) can chime in??

[图片] philh: @Falco I this still the case? Yes, all the sites we host use the S3 plus CloudFront combo. Even this site you are browsing right now.

Thanks for confirming! After seeing this I re-adjusted DISCOURSE_S3_CDN_URL: back to amazonassigned.cloudfront.net hoping it my clear the cert and url issues. [Screenshot 2025-12-11 133250] The rebuilt and re ran all the rakes mentioned in docs. rake posts:rebake rake uploads:migrate_to_s3 still generates FileStore::ToS3MigrationError rake posts:rebake_uncooked_posts rake s3:upload_assets rake s3:expire_missing_assets Still no joy on getting the site to load. Any suggestions?

[图片] philh: Looking at AWS Alternate domain names as a possible solution. Turns out this was helpful. [Screenshot 2025-12-12 001849]

AWS CDN 和 S3 的问题

产品支持安装

Falco (Falco) 2025 年12 月 11 日 21:21 12

是的，我们托管的所有站点都使用 S3 加上 CloudFront 的组合。您现在正在浏览的这个站点也是如此。

话题		回复	浏览量
Configure an S3 compatible object storage provider for uploads Self-Hosting cdn , configuring , how-to , reference	267	54770	2026 年9 月 15 日
Unable to setup S3 bucket Self-hosting uploads , s3	11	751	2025 年1 月 12 日
Defining DISCOURSE_S3_CDN_URL links to assets in S3 CDN URL Product Support	42	7666	2020 年4 月 22 日
Set up file and image uploads to S3 Self-Hosting configuring , how-to	35	122330	2025 年10 月 25 日
Configuring AWS's Amazon S3 for storage and Cloudfront for CDNs Sysadmins cdn , s3	2	405	2026 年1 月 13 日

AWS CDN 和 S3 的问题

相关话题