I had a discourse update fail on my Digital Ocean droplet. Tried to restore a droplet backup and it doesn’t seem like discourse is in the new droplet from the backup. Spun up a new droplet, installed fresh discourse and it sees my amazon S3 backups. Click restore and the site has all the posts etc but all of a sudden the restore fails and it rolls back. Not sure why that’s happening and what to do next to get my discourse running. I have attached the log file for reference.
log 3.txt (93.8 KB)
569 posts are not remapped to new S3 upload URL. S3 migration failed for db ‘default’.
The fact that it says there is a new S3 upload URL indicates that you have configured it differently from the former situation. The fact that it fails indicates that the new configuration is also incorrect.
Solution: make sure the variables set in your app.yml are the same as on the prior install.
1 Like
I grabbed the app.yml file from the failed discourse update droplet and moved to the new droplet I’m trying to restore the backup to. Still fails the 569 posts. Is there a way to skip those or another way to get past that? I’d rather have the whole forum back up vs 569 posts.
My usual trick is to disable s3 uploads before making the move, but I assume you don’t have that choice since your original forum is down.
I am not 100% sure if this would work - you could try this
- set
DISCOURSE_ENABLE_S3_UPLOADS: falsein your app.yml - restore
- remove that line
- rebuild
If it doesn’t work then you could try to edit the dump.sql file in the backup and set the setting to false there.