Hello guys, How can I completely turn off AWS S3 storage and bring back all the files and backup in the S3 storage back to my EC2 server?

I believe this will do the trick: ./launcher enter app rake uploads:migrate_from_s3 rake posts:rebake This migrates uploads FROM S3 to your web server. Then you can go back to your app.yml and change DISCOURSE_USE_S3: false. Then rebuild.

I would also go in the admin area of discourse and uncheck all the boxes that activate S3 mode.

I did as mentioned by @AntiMetaman but it gives me an error rake aborted. First, it asks me to turn off S3 upload. I turned of s3 upload and tried rake again, then this error pops up. root@ip-172-31-7-247-app:/var/www/discourse# rake uploads:migrate_from_s3 --trace ** Invoke uploads:migrate_from_s3 (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute uploads:migrate_from_s3 Migrating uploads from S3 to local storage for 'default'... rake aborted! NoMethodError: undefined method `downcase' for nil:NilClass /var/www/discourse/app/models/global_setting.rb:107:in `s3_bucket_name' /var/www/discourse/app/models/site_setting.rb:157:in `absolute_base_url' /var/www/discourse/lib/tasks/uploads.rake:138:in `migrate_from_s3' /var/www/discourse/lib/tasks/uploads.rake:118:in `block in migrate_all_from_s3' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rails_multisite-2.3.0/lib/rails_multisite/connection_management.rb:68:in `with_connection' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rails_multisite-2.3.0/lib/rails_multisite/connection_management.rb:78:in `each_connection' /var/www/discourse/lib/tasks/uploads.rake:118:in `migrate_all_from_s3' /var/www/discourse/lib/tasks/uploads.rake:93:in `block in ' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `block in execute' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `each' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `execute' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:219:in `block in invoke_with_call_chain' /usr/local/lib/ruby/2.6.0/monitor.rb:235:in `mon_synchronize' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:199:in `invoke_with_call_chain' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:188:in `invoke' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:160:in `invoke_task' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `block (2 levels) in top_level' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `each' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `block in top_level' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:125:in `run_with_threads' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:110:in `top_level' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:83:in `block in run' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:186:in `standard_exception_handling' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:80:in `run' bin/rake:13:in ` ' /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:63:in `load' /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:63:in `kernel_load' /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:28:in `run' /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli.rb:476:in `exec' /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run' /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command' /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor.rb:399:in `dispatch' /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli.rb:30:in `dispatch' /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/base.rb:476:in `start' /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/cli.rb:24:in `start' /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/exe/bundle:46:in `block in ' /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/lib/bundler/friendly_errors.rb:123:in `with_friendly_errors' /usr/local/lib/ruby/gems/2.6.0/gems/bundler-2.1.4/exe/bundle:34:in ` ' /usr/local/bin/bundle:23:in `load' /usr/local/bin/bundle:23:in ` ' Tasks: TOP => uploads:migrate_from_s3

I came across this topic today. Might be worth holding off if you can. [image] Migrate_from_s3 problems Bug When migrating from S3 to local storage, we see a number of issues. The main issue is that the migrate_from_s3 rake task is not taking the Uploads table as a starting point, but the posts. This causes it to skip a lot of uploads which are being left on S3. uploads used as logo’s because they are not referenced in a post uploads for avatars because they are not referenced in a post uploads that are (for some reason) referenced by their CDN URL in raw because they do not match the regex that is…

If you turn off S3 only from the admin panel, that only disables it at site level. You want to globally disable it which is why you have to change the value from true to false in the app.yml and then rebuild. It should work if you setup your S3. I just tried a migrate_from_s3 and migrate_to_s3. It works for me. I haven’t gotten any errors. I don’t know what this error means so a Discourse dev at this point should help: NoMethodError: undefined method downcase’ for nil:NilClass`

Strange my reply below was deleted; so I am posting it again. [image] AntiMetaman: I don’t know what this error means so a Discourse dev at this point should help: NoMethodError: undefined method downcase’ for nil:NilClass` That error occurs when a string method is called on an object which is nil; and generally happens in Ruby when a string object is expected, but it is nil. That is why that error occurs.

Added DISCOURSE_USE_S3: false to app.yml but still the same error. Which version of discourse are you using? I am using the latest version.

I am also on latest. Did you get any errors on rebuild? If so, can you post those?

How to turn off S3 storage?

Product Support Self-hosting

SouperC (NotSoSuper) August 11, 2020, 6:09am 6

I came across this topic today. Might be worth holding off if you can.

Topic		Replies	Views
Migrate_from_s3: You must disable S3 uploads before running that task Product Support	21	1611	September 19, 2020
Rake uploads:migrate_from_s3 fails Self-hosting s3	31	3623	April 24, 2021
Rake uploads:migrate_to_s3 error Self-hosting s3	8	1032	January 6, 2020
Migrate_to_s3 for Digital Ocean Spaces woes Self-hosting s3	25	3617	March 28, 2019
Stop using Amazon s3 for uploads Product Support	51	5858	August 22, 2021

How to turn off S3 storage?

Related topics