Rclone SFTP backup errors are easier to fix when you know where the job failed. In this guide, you will learn to fix the errors, from permission-denied messages to timeouts and failed syncs. You can use SSH tests and debug logs to find the cause, then retry safely and verify your files.
Fix Rclone SFTP Backup Failures: Permissions, Timeouts, and Sync Errors
Table of Contents

Symptoms of Rclone SFTP Backup Errors
You can find the error message or symptom in the table below to see what to check first and how to fix it.
1. Test SSH with the Backup Job’s Key
Run these commands on the source machine as the same local user that runs the scheduled job. Replace the example host, port, key, and paths with yours. This guide assumes an existing rclone SFTP remote named backup:
The SSH command requests the SFTP subsystem, not a shell. Once the log confirms authentication and subsystem startup, press Ctrl+C and use the SFTP client for an interactive test:
If both commands reject the key, check whether the server has the matching public key and permits that account and source IP.
On Ubuntu, an administrator can run the command below to check the latest SSH logs:
If SFTP works but rclone fails, check which config file and private key the backup job uses. If your manual test uses an SSH agent, make sure the job can access it too.
Set known_hosts_file to a trusted file. If the server’s host key changes, ask the server administrator to confirm the new fingerprint before updating the file.
If Rclone SFTP backup errors happen only during scheduled runs, check which user runs the job and which config file it loads. If it loads the wrong file, add --config /path/to/rclone.conf to the scheduled command.
2. Check the Backup Folder and Its Permissions
A chroot limits which folders the SFTP user can see. For example, /srv/sftp/client1/backups on the server might appear as /backups to that user.
In rclone, backup:/backups looks for the folder at the top of the SFTP account’s visible folders. Without the leading slash, backup:backups looks for it inside the account’s login folder.
Run this command to list the files and folders in /backups and show detailed logs:
If you can list the files, you can see what’s in the folder. To check whether you can write to it, create a small local file at /tmp/backup-probe.txt. Then, run these commands at the SFTP prompt. Make sure both remote test names are unused before you start:
pwd shows your current folder. The next commands open /backups, upload the test file, rename it, and remove it. If a command fails, stop there and note the error.
If you see Rclone SFTP backup errors after login, check the folder permissions on the backup server:
The chroot folder and its parent folders must be owned by root. Group members and other users must not be able to write to them.
Give the backup user write access to /backups inside the chroot, not to the chroot folder itself. You can see how to create SFTP-only backup users on Ubuntu for the full setup.
3. Troubleshoot SFTP Connection Timeouts
If Rclone SFTP backup errors happen before login, you must check the SSH log. Look for a hostname that can’t be found, a refused connection, or a timeout.
Check the port in your rclone config, then run sudo ss -ltnp on the backup server to see if SSH is listening on that port. If an upload starts but fails later, note when it failed and check both logs for that time.
--contimeoutsets how long rclone waits to connect.--timeoutsets how long rclone waits with no data sent or received. It does not limit the total backup time.
If rclone uses an external SSH client, set the connection timeout in that client. Longer timeouts won’t open a blocked port or fix a connection that keeps dropping.
4. Check Storage Limits and Failed Uploads
Run these commands on the destination as an administrator, using the real server path:
df -h shows how much disk space is free. df -i shows how many more files the filesystem can track.
Also, check the backup user’s storage limit. The user may have reached it even if the disk still has space. If growing backups keep causing Rclone SFTP backup errors, check how long you need to keep old backups and how much space they need before comparing dedicated server hosting.
A .partial file may be an upload that hasn’t finished. Make sure no backup is running before you touch it. Fix the cause, then run the transfer again. Don’t rename the incomplete file or assume rclone will pick up where it stopped.
5. Test the Sync and Retry the Backup Safely
Before you retry, make sure the source folder contains the files you expect. If the files are on a mounted drive, check that the drive is mounted. Then, run a dry run to preview the sync and save a private debug log:
Check the dry-run log to see which files sync would be deleted. A dry run does not test whether you can upload or rename files.
Use copy if you want to keep files that exist only on the backup server. It can still replace changed files with the same path. If you want the backup to match the source, run another dry run with your final options. Run sync only if you’re sure the listed files can be deleted.
Run this command to copy files to /backups over SFTP with retries and a speed limit, and save the log to $LOG:
Rclone tries up to three times, waits 15 seconds before each retry, and limits the total transfer speed to about 5 MiB/s. It allows up to two transfers and two file checks in parallel.
To track Rclone SFTP backup errors, save a separate log for each run and set an alert if rclone exits with a code other than 0. After the job finishes, run this command to delete logs older than 30 days:
6. Verify the Backup Data
Rclone SFTP backup errors about hashes do not always mean the files differ. Rclone usually needs remote shell access to calculate hashes on the server. For an SFTP-only account, set shell_type = none in the remote config. Then, use this command to compare the file contents over SFTP:
--one-way checks that every source file has a matching backup and ignores extra files on the backup server. Remove it to check for extra files too.
--download reads the remote files to compare their contents, so it uses bandwidth. Run the check when the source files are not changing. If a file does not match, copy it again from a trusted source, then repeat the check.
Conclusion
To fix Rclone SFTP backup errors, check your login, folder permissions, disk space, and connection logs. Preview the changes before retrying, then check that the files match and test restoring a few files.
If you need a separate backup server, compare Linux VPS hosting plans and choose enough space for the backups you want to keep.
For a full setup guide, you can check this guide on how to sync files to a Storage VPS with Rclone.
The job may run as a different user or lack access to your config, key, or SSH agent.
No. Retries can help with brief connection drops, not wrong keys, blocked paths, or full disks.
No. It leaves destination-only files in place but can replace files with the same path. Use separate versioned backups if you need older copies.