A user, zachwlewis, is trying to restore a backup of an older version to a fresh install of Discourse after a failed update resulted in data loss. Falco suggests uploading a backup to /admin/backups, enabling the allow restore setting, and clicking restore. However, zachwlewis encounters an issue logging in due to the site being in read-only mode. Falco provides a solution by accessing the admin login page directly using /users/admin-login. When this fails, Falco guides zachwlewis to disable read-only mode via the command line.
After successfully logging in, zachwlewis thanks Falco for the assistance. It’s also noted by tgxworld that the data may not be lost and can be found in postgres_data_old in /var/discourse/shared/standalone.
After following the steps on the Discourse update page, I was asked to update via the command line. When updating via the command line, I was asked to update my app.yml, and the update essentially attempted to downgrade my postgresql install, resulting in all my data being lost. Luckily, I have several backups in an S3 bucket.
After a bit of work, my Discourse install was running, but it was a totally fresh copy. I pointed the backups directory to the S3 bucket, but was unable to see any of my old backups. To test that everything was configured correctly, I ran a manual backup, which appeared both in my Discourse Backups page and in the S3 bucket (alongside the previous backups).
I made very sure to keep lots of backups in case I somehow lost all my data. How can I restore from these backups?
So, I’m attempting to log in to the site, and it says I’m not allowed to log in because it’s in read-only mode. I specifically set the site to read-only mode until I was able to restore the data. How do I log in?