Hi folks!
Ran into some data export-restore kind of issues and would request your help.
Context:
Wanted to export data from Discourse Teams to a self-hosted droplet on digital ocean.
Backup, restore went smoothly. No issues. But post the restore, here’s what discourse shows:
Hi Yash! Sorry to hear you’re having some trouble with the backup/restore. Have you tried safe mode yet? Just add /safe-mode to the end of the URL. You can then see what hapens when you disable the current theme, unofficial plugins or all plugins.
I also recommend you take a look at /logs and the nginx error log to see if there are any errors that might help you further.
And what happens when you run ./launcher rebuild app from the command line? You may want to try running it multiple times. This has worked for me in the past.
And finally, can you share the contents of your containers/app.yml file (without passwords and site identifying info please) so we can see what plugins you have installed.
Hey Tobias,
Thank you so much for the prompt reply. Genuinely appreciate your help.
When i go to /safe-mode it gives me a few checkbox options such as disable theme etc. Once I check all of them and click next, it’s the same error on the frontend.
The url appended was /?safe_mode=no_custom%2Cno_plugins%2Conly_official
Please note, this is the one-click DO droplet with no additional plugins installed by me yet.
But the Teams instance had a lot of plugins. Do you reckon that’s causing the issue?
Hey @tobiaseigen
I setup a new droplet, installed discourse following the instructions on github. Logged in, uploaded the backup, restore - same error.
It’s an issue with uploads. It’s looking for an S3 bucket name but the new environment is not configured with one.
How was the backup created and are all uploads included? I don’t see any uploads happening in the restore log, which suggests there were none in the backup.
I just did a quick test of the backup process and see that the uploads are indeed included in the backup file. Tomorrow I will see if I can figure out how to restore this to a fresh self-hosted site.
Hi @schleifer - As Tobias rightly pointed out, the backup was created from teams (the usual backup download). When i clicked on cancel subscription, it gave me an option to backup and download that backup. Post that I have taken a separate backup from the admin panel. Both have the same file size, and neither of them work on the self-hosted install.
@pfaffman - No no, the site was still active when I made the backup. I’m not sure about the hidden setting. Maybe that could be the issue.
@tobiaseigen - When i unzip the tar.gz file, the only content is “dump.sql”. I don’t see any media/ attachments. Did I do something wrong when I took the backup?
Yeah. That’s not the backup you need. If you have only the sql dump then you’re going to need to check with them and get the backup with the uploads. I’m pretty sure they’ll get it sorted out tomorrow and you’ll be all good.
I had the same thoughts - if the files are missing, shouldn’t discourse still show all the threads, external links and conversations without the natively uploaded attachments?
I think that if he pulls out the dump.sql.gz and renames it with the full-dump-filename.sql.gz it’ll restore but if it had the tar.gz name it tries to process uploads and fails. (Maybe there is S3 stuff in the site settings? I don’t quite get it.) There was a similar topic last week and that was Gerhard’s recommendation.
But if he really wants to host the site, he wants the uploads, so he might as well wait for the full dump.
@biyaniyash can you please go to /admin/site_settings/category/all_results?filter=s3 on your new site and disable everything related to s3, then give it another shot? That should get your site working.
Hey @tobiaseigen:
This is what I see by default when I go to /admin/site_settings/category/all_results?filter=s3 on the new self-hosted discourse site:
