Hi! I’ve just installed Discourse on a new server and now I’m trying to upload a backup with about 400MB. It stucks at 40% with the following error: Slow down, too many requests from this IP address. Please retry again in 2 seconds. Error code: ip_10_secs_limit. What is this and how can I solve it?

I followed your link to restore the backup from CLI, but nothing was restored, it was still the same as a fresh install. Is in the backup the “old” app.yml file and will it be overwritten when I restore the backup? If not, the whole backup is useless. I tried to restore the backup than from within Discourse and now I have a blank site. This is from the command line when I try to restore the backup. Of course I followed the commands from the link, but it seems that something has changed. Starting restore: backup-2021-12-06-185610-v20211201221028.tar.gz [STARTED] 'system' has started the restore! Marking restore as running... Making sure /var/www/discourse/tmp/restores/default/2021-12-18-163225 exists... Copying archive to tmp directory... EXCEPTION: lib/discourse.rb:127:in `exec': Failed to copy archive to tmp directory. cp: cannot stat '/var/www/discourse/public/backups/default/backup-2021-12-06-185610-v20211201221028.tar.gz': No such file or directory lib/discourse.rb:154:in `execute_command' lib/discourse.rb:127:in `exec' lib/discourse.rb:34:in `execute_command' /var/www/discourse/lib/backup_restore/local_backup_store.rb:42:in `download_file' /var/www/discourse/lib/backup_restore/backup_file_handler.rb:62:in `copy_archive_to_tmp_directory' /var/www/discourse/lib/backup_restore/backup_file_handler.rb:22:in `decompress' /var/www/discourse/lib/backup_restore/restorer.rb:42:in `run' script/discourse:149:in `restore' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.1.0/lib/thor/command.rb:27:in `run' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.1.0/lib/thor/invocation.rb:127:in `invoke_command' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.1.0/lib/thor.rb:392:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.1.0/lib/thor/base.rb:485:in `start' script/discourse:290:in ` ' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.26/lib/bundler/cli/exec.rb:58:in `load' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.26/lib/bundler/cli/exec.rb:58:in `kernel_load' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.26/lib/bundler/cli/exec.rb:23:in `run' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.26/lib/bundler/cli.rb:477:in `exec' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.26/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.26/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.26/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.26/lib/bundler/cli.rb:31:in `dispatch' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.26/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.26/lib/bundler/cli.rb:25:in `start' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.26/exe/bundle:49:in `block in ' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.26/lib/bundler/friendly_errors.rb:128:in `with_friendly_errors' /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.26/exe/bundle:37:in ` ' /usr/local/bin/bundle:23:in `load' /usr/local/bin/bundle:23:in ` ' Trying to rollback... There was no need to rollback Cleaning stuff up... Removing tmp '/var/www/discourse/tmp/restores/default/2021-12-18-163225' directory... Marking restore as finished... Notifying 'system' of the end of the restore... Finished! [FAILED] Restore done.

[image] daemon: No such file or directory So you put the file in the wrong place or for the filename wrong. If it’s the latter, then discourse restore With no filename will suggest the files available. If you do a discourse backup You can see where it put the file. I won’t try to type the proper path on my phone.

[image] pfaffman: So you put the file in the wrong place or for the filename wrong. If it’s the latter, then No, I did it like it’s written here: [image] Restore a backup from the command line Self-Hosting bookmark This guide explains how to restore a Discourse backup from the command line without using the Discourse web UI. person_raising_hand Required user level: Administrator wrench Console access required Here’s how to restore a Discourse backup from the command line, without ever booting the Discourse web UI. This is handy when you’re moving servers. Prerequisites Before you start, make sure you complete the following steps: Download the latest backup file from the source Disco… [image]Restore a backup from the command line Transfer Backup SSH into the destination server, or otherwise create the backup folder there: mkdir -p /var/discourse/shared/standalone/backups/default Upload your backup file to the destination server. scp /path/to/backup/backup.tar.gz root@192.168.1.1:/var/discourse/shared/standalone/backups/default Of course, replace the above paths, filenames, and server names with the ones you are using – but you do want the backup file to end up in /var/discourse/shared/standalone/backups/default :mega: You can also upload and download your Discourse backup file from popular web storage sites such as Google Drive, Dropbox, OneDrive, etc – you’ll need to look up the specific command line instructions based on your preferred web storage provider. :warning: DO NOT CHANGE THE FILENAME OF THE BACKUP! Discourse treats the backup filename as metadata, so if you change the filename, restoring will not work. Stick with the original file name. Replace /path/to/backup/discourse-xyz.tar.gz with the local path of your backup file, and replace with the IP address of destination server. So if this is the wrong path, the tutorial is wrong. That’s why I asked where to put the file.

It’s really easy to type things wrong. That’s why I suggested ways to test that you got things in the right place. Did you try discourse restore With no filename?

I know what you mean. but I did it exactly according to the instructions (without making a mistake, I copied the paths), so I ask if the instructions are wrong or if something has changed in the paths in the last 2 years. I will try it again, but maybe I have to reinstall Discourse again because now I have only a blank site.

[image]Restore a backup from the command line Upload your backup file to the destination server. scp /path/to/backup/backup.tar.gz root@192.168.1.1:/var/discourse/shared/standalone/backups/default Of course, replace the above paths, filenames, and server names with the ones you are using I don’t think you can copy and paste this bit without changing it?

I think the destination path is the right, otherwise they should say where exactly to move it.

Ah, I see. I read your post as ‘I couldn’t have mistyped anything as I copied and pasted it all from the guide’. :slightly_smiling_face:

So I could restore the backup with discourse restore, but some categories are missing, the whole header is missing, I can’t login, the app.yml is still the same as a fresh install and many more. The backup was from 06.12.21 and I chose to backup everything, but half of the things are missing. So for me the whole backup and restore process is a totally mess!

This must be incredibly frustrating. You have my sympathies. The app.yml isn’t included in the Discourse backup. You would need to copy one over from your old instance, or edit a new one.

Can't upload backup

Product Support

JammyDodger December 19, 2021, 9:48am 8

I don’t think you can copy and paste this bit without changing it?

Topic		Replies	Views
Help restoring - system hung at midnight Self-hosting	26	2943	June 13, 2022
Implosion after 2.7beta7 upgrade Product Support	18	1554	April 27, 2021
Issues with restoring backup to discourse Product Support backups	17	546	March 21, 2025
Can't restore from backup Self-hosting	12	2537	January 16, 2018
Errors on Exporting Data from Teams to Self Hosted Discourse on Digital Ocean Product Support	39	2411	May 12, 2021

Can't upload backup

Related topics