Can't upload backup

[daemon (Alex)]

@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:

Restore a backup from command line

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 Download the latest backup file from source Discourse instance. The destination discourse needs to be bootstrapped (run ./discourse-setup or copy your existing app.yml) Make sure that the destination Discourse instance is on the latest version. Update it if necessary. Transfer Backup SSH into the destination server, or otherwise c…

@techAPJ

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

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.

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 <server_ip_address> 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.