I setup a new host so I can have a ‘staging’ environment. I re-created the same discourse installation with what should be the same version. I’m running version: 2.8.2. First comment, as of version 2.8.2 my back up size has dropped from 282MB to around 90MB. Not sure why but I’m going to just with some intelligence added in that I’m taking advantage of. I downloaded the latest archive from my forum, and uploaded to local storage on the new staging environment. The restore fails due to: [2022-02-27 19:41:18] ALTER TABLE [2022-02-27 19:41:18] ALTER TABLE [2022-02-27 19:41:18] Migrating the database... [2022-02-27 19:43:00] [2022-02-27 19:43:00] Reconnecting to the database... [2022-02-27 19:43:00] Reloading site settings... [2022-02-27 19:43:00] Disabling outgoing emails for non-staff users... [2022-02-27 19:43:02] Disabling readonly mode... [2022-02-27 19:43:02] Clearing category cache... [2022-02-27 19:43:02] Reloading translations... [2022-02-27 19:43:02] Remapping uploads... [2022-02-27 19:43:02] Remapping 'https://forum.geekbeacon.org' to 'https://forum-staging.geekbeacon.org' [2022-02-27 19:43:08] Restoring uploads, this may take a while... [2022-02-27 19:43:36] EXCEPTION: 8 posts are not remapped to new S3 upload URL. S3 migration failed for db 'default'. [2022-02-27 19:43:36] /var/www/discourse/lib/file_store/to_s3_migration.rb:132:in `raise_or_log' /var/www/discourse/lib/file_store/to_s3_migration.rb:87:in `migration_successful?' /var/www/discourse/lib/file_store/to_s3_migration.rb:373:in `migrate_to_s3' /var/www/discourse/lib/file_store/to_s3_migration.rb:66:in `migrate' /var/www/discourse/lib/file_store/s3_store.rb:317:in `copy_from' /var/www/discourse/lib/backup_restore/uploads_restorer.rb:62:in `restore_uploads' /var/www/discourse/lib/backup_restore/uploads_restorer.rb:44:in `restore' /var/www/discourse/lib/backup_restore/restorer.rb:61:in `run' /var/www/discourse/script/spawn_backup_restore.rb:23:in `restore' /var/www/discourse/script/spawn_backup_restore.rb:36:in `block in ' /var/www/discourse/script/spawn_backup_restore.rb:4:in `fork' /var/www/discourse/script/spawn_backup_restore.rb:4:in ` ' [2022-02-27 19:43:36] Trying to rollback... [2022-02-27 19:43:36] Rolling back... [2022-02-27 19:43:36] Cleaning stuff up... [2022-02-27 19:43:36] Dropping functions from the discourse_functions schema... [2022-02-27 19:43:36] Removing tmp '/var/www/discourse/tmp/restores/default/2022-02-27-194051' directory... [2022-02-27 19:43:36] Unpausing sidekiq... [2022-02-27 19:43:36] Marking restore as finished... [2022-02-27 19:43:36] Notifying 'csgeek' of the end of the restore...

[image] Samir_Faci: EXCEPTION: 8 posts are not remapped to new S3 upload URL. S3 migration failed This is your issue. Maybe use the same S3 bucket and use the same bucket? Maybe see that the hidden setting that’s called something like "download S3 in backup " is turned on. You’ll need to search or look on on the source for the setting name. Or maybe you need to see that the rest of your uploads on the production site are on S3.

I have no S3 configured I’m guessing maybe the old server has some old data that didn’t get mapped to a valid S3 location. I went back to the older server and I have 2 buckets configured, 1 for backups and 1 for media. I followed the guide and setup AWS S3 including the CDN. When I run rake uploads:migrate_to_s3 which failed, I follwed that with a posts:rebake and that seems to have reduced the number of errors, but it still fails: Please note that migrating to S3 is currently not reversible! [CTRL+c] to cancel, [ENTER] to continue Migrating uploads to S3 for 'default'... Uploading files to S3... - Listing local files => 208 files - Listing S3 files . => 978 files - Syncing files to S3 ................................................................................................................................................................................................................ Updating the URLs in the database... Removing old optimized images... Flagging all posts containing lightboxes for rebake... 15 posts were flagged for a rebake rake aborted! FileStore::ToS3MigrationError: 1 posts are not remapped to new S3 upload URL. S3 migration failed for db 'default'. /var/www/discourse/lib/file_store/to_s3_migration.rb:132:in `raise_or_log' /var/www/discourse/lib/file_store/to_s3_migration.rb:87:in `migration_successful?' /var/www/discourse/lib/file_store/to_s3_migration.rb:373:in `migrate_to_s3' /var/www/discourse/lib/file_store/to_s3_migration.rb:66:in `migrate' /var/www/discourse/lib/tasks/uploads.rake:123:in `migrate_to_s3' /var/www/discourse/lib/tasks/uploads.rake:102:in `block in migrate_to_s3_all_sites' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rails_multisite-4.0.0/lib/rails_multisite/connection_management.rb:80:in `with_connection' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rails_multisite-4.0.0/lib/rails_multisite/connection_management.rb:90:in `each_connection' /var/www/discourse/lib/tasks/uploads.rake:100:in `migrate_to_s3_all_sites' /var/www/discourse/lib/tasks/uploads.rake:96:in `block in ' /usr/local/bin/bundle:25:in `load' /usr/local/bin/bundle:25:in ` ' Tasks: TOP => uploads:migrate_to_s3 (See full trace by running task with --trace) Is there a way to run migrate_to_s3 in a verbose mode to identify the post that’s the culprit?

Your restore is failing with an error like this? FileStore::ToS3MigrationError: 1 posts are not remapped to new S3 upload URL. S3 migration failed for db 'default'. In that case the best thing to do is fix up the post(s) that have uploads in the wrong place. But I think that there’s a case in which that test can have a false positive. In that case, you can use a switch on the rake task the will have it pause so you can fix things up. I can’t find it quicky, and it’s not at Backup discourse from the command line where it should be. I’m in the middle of a task, so I can’t find it now.

[image] pfaffman: FileStore::ToS3MigrationError: 1 Yes I have this kind of error EXCEPTION: 3 posts are not remapped to new S3 upload URL. S3 migration failed for db ‘default’

You can try discourse restore --pause filename That’ll pause the restore and you can muck with the database in another terminal to fix it. Or, I think, you can just stop it before it does that check.

I must use this during a comand line restore I think

Same error: Uploading files to S3… * Listing local files => 2 files * Listing S3 files … => 183549 files * Syncing files to S3 .. Updating the URLs in the database… Removing old optimized images… Flagging all posts containing lightboxes for rebake… 169809 posts were flagged for a rebake **EXCEPTION: 3 posts are not remapped to new S3 upload URL. S3 migration failed for db ‘default’.** /var/www/discourse/lib/file_store/to_s3_migration.rb:132:in `raise_or_log' /var/www/discourse/lib/file_store/to_s3_migration.rb:81:in `migration_successful?’ /var/www/discourse/lib/file_store/to_s3_migration.rb:385:in `migrate_to_s3' /var/www/discourse/lib/file_store/to_s3_migration.rb:59:in `migrate’ /var/www/discourse/lib/file_store/s3_store.rb:367:in `copy_from' /var/www/discourse/lib/backup_restore/uploads_restorer.rb:69:in `restore_uploads’ /var/www/discourse/lib/backup_restore/uploads_restorer.rb:49:in `restore' /var/www/discourse/lib/backup_restore/restorer.rb:179:in `restore_uploads’ /var/www/discourse/lib/backup_restore/restorer.rb:72:in `run' script/discourse:243:in `restore’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.4.0/lib/thor/command.rb:28:in `run' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.4.0/lib/thor/invocation.rb:127:in `invoke_command’ /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.4.0/lib/thor.rb:538:in `dispatch' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.4.0/lib/thor/base.rb:584:in `start’ script/discourse:397:in ` ' /usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/cli/exec.rb:59:in `load’ /usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/cli/exec.rb:59:in `kernel_load' /usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/cli/exec.rb:23:in `run’ /usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/cli.rb:452:in `exec' /usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/vendor/thor/lib/thor/command.rb:28:in `run’ /usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command' /usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/vendor/thor/lib/thor.rb:538:in `dispatch’ /usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/cli.rb:35:in `dispatch' /usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/vendor/thor/lib/thor/base.rb:584:in `start’ /usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/cli.rb:29:in `start' /usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/exe/bundle:28:in `block in ’ /usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors' /usr/local/lib/ruby/gems/3.3.0/gems/bundler-2.6.4/exe/bundle:20:in ` ’ /usr/local/bin/bundle:25:in `load' /usr/local/bin/bundle:25:in `’ Trying to rollback… Rolling back… Cleaning stuff up… Dropping functions from the discourse_functions schema… Removing tmp ‘/var/www/discourse/tmp/restores/default/2026-01-13-145033’ directory… Unpausing sidekiq… Marking restore as finished… Notifying ‘system’ of the end of the restore… Finished!

You either need to fix those three Uploads or stop the restore before it does that check.

How could I find 3 post on 168000? Is it possible to stop the restore, skipping this veryfing?

Restore to New Host

Product Support

Saiano (Saiano) January 13, 2026, 2:06pm 4

I have the same problem, migrating myserver without changing s3 bucket.
Any suggestion?

Topic		Replies	Views
Restore process cancelled at migrating uploads to S3 step Product Support	48	4025	January 24, 2026
Restore fails due to s3 migration failure Product Support	2	168	August 12, 2026
Intended path to migrate S3 to local Self-hosting uploads , s3	5	990	May 13, 2023
Restore failed at "EXCEPTION: x of y uploads are not migrated to S3. S3 migration failed for db 'default'." Self-hosting	4	1270	June 10, 2022
Restore from backup fails due to S3 migration Product Support	8	1536	September 10, 2019

Restore to New Host

Related topics