Okay this was bound to happen, things were just too good for too long. Years of running on cruise control, the system would automatically update itself and I would update Discourse every few weeks. At midnight last night, Amazon showed the system was unresponsive, discourse was down and the CPU was …

Hi, after recreating the new server from the app.yml, did you have access to the backups in the https://your.domain/admin/backups section ?

No, after recreating from app.yml it just gave me a clean new setup with nothing. I downloaded the last backup from S3 and manually uploaded it to discourse locally and hit restore. I starts restoring it, I see all the settings (including the S3, the credentials everything from the Settings page) c…

No I don’t see this in my app.yml All the S3 settings were defined in the Admin → Settings pages and it was working fine for year until I needed to restore it when the server went down last night. [image] Benjamin_D: But configured as in Setting up file and image uploads to S3 Correct, this…

I think I would try editing the app.yml with your settings and from there I believe (hope?) you should see your backups in the admin section and restore from there, without the manual import and the uploads, which you shouldn’t have to restore, but seem to be included in the backups. I don’t know wh…

I think this may be because your backup contains a mix of S3 and local uploads. I’m afraid it’s not my area of expertise, but there is some discussion and a workaround in this topic which allows you to bypass the failure. However, it was for a much smaller number of errors so you may want to take th…

Thanks, my site has crashed unfortunately so I’m only left with the S3 uploads and back ups. I’m assuming there’s no way to for me to migrate any left over local files to the S3 now. So I’m wondering what are my options right now? Is there a way to restore from S3 backups and ignore the local files…

So an update for folks who may be struggling with the same issue (basically I’m unable to restore from a backup and the server crashed due to a fault system upgrade). From what I understand the root cause of the issue is that there are local uploads AND there are S3 uploads, so when the restore too…

If you configure as described in Using Object Storage for Uploads (S3 & Clones) you should be able to rake uploads:migrate_to_s3 If you want to stop using s3, then you can enter the rails console and set SiteSetting.include_s3_uploads_in_backups=true Then take a backup, make sure that you do n…

Okay I think I got a little mixed up here. I’m thinking the ideal thing to do would probably be to have all uploads local and save the backups (zips) to the S3. This way the backup is available on S3 should anything happen to the server but the backup in itself is self contained with no dependencie…

Help restoring - system hung at midnight

Support Self-hosting

Benjamin_D (Benjamin Decotte) June 9, 2022, 10:06am 4

so the s3 config isn’t in the app.yml (as described here Configure an S3 compatible object storage provider for uploads )? But configured as in Set up file and image uploads to S3

Topic		Replies	Views
Restore failed at "EXCEPTION: x of y uploads are not migrated to S3. S3 migration failed for db 'default'." Self-hosting	4	1110	June 10, 2022
Restore process cancelled at migrating uploads to S3 step Support	49	2931	January 24, 2026
Intended path to migrate S3 to local Self-hosting uploads , s3	5	865	May 13, 2023
Restore to New Host Support	13	655	January 15, 2026
Implosion after 2.7beta7 upgrade Support	18	1281	April 27, 2021

Help restoring - system hung at midnight

Related topics