Hi, I’m trying to upload my backup to my new server, but it doesn’t seem to be working. The same issue occurs when I try to upload it to my current server. The upload gets stuck at 0% and doesn’t progress on either my old (where I downloaded my backup from) or new server (fresh Discourse). Both ‘Enable backups’ and Allow restore” are enabled.
AI-generated summary
The user Cate_Soule is experiencing issues uploading a backup to their server, with the upload stalling at 0%. Ethsim2 suggests this may be due to an nginx hard limit and recommends using SCP to transfer the backup file directly via SSH, providing command examples for macOS users. Cate_Soule confirms they are using a Mac, and Ethsim2 clarifies the correct SCP command. The issue appears resolved, as Cate_Soule confirms port 22 is open. Ethsim2 explains the solution involves using SCP to bypass the upload limit, and tobiaseigen asks for confirmation of success.
this is likely an nginx hard limit.
Do you have a windows PC?
I would recommend opening port 22 and running the following in command prompt
scp -C ./<<<backup file name>>>.tar.gz root@<<<domain.com>>>:/var/discourse/shared/standalone/backups/default/
Not windows PC. I have mac.
Press ⌘ + Space → type Terminal → Enter
Run your command
scp -C root@domain.com:/var/discourse/shared/standalone/backups/default/cate-s-community-2025-10-17-161933-v20251016143343.tar.gz .
- -C → enables compression
- root@domain.com: → your server’s login
- /var/discourse/…tar.gz → remote path
- . → save it in your current local directory (e.g. /Users/yourname)
make sure you have a strong root password, and if you use SSH key the scp command will need to be modified
It seems that port 22 is already open.
this is the command you want for upload from mac to server
you’ll need to save your tarball backup file in the directory of terminal where you’ll run that command
@Cate_Soule did that work for you? If so, please select the solution button on one of Ethan’s posts and we can close this topic.