Fix Files.com Sync Errors — Connection, Transfer, and Missing File Problems Resolved with RcloneView
When a Files.com job fails, RcloneView's job history, DEBUG logs, and Folder Compare show whether the cause is the remote, the transfer load, or files that never arrived.
A Files.com sync that stops with a vague error, or finishes with folders that look incomplete, is hard to diagnose from the command line alone. RcloneView puts the remote check, the job record, the log, and a side-by-side comparison in one window, so you can work from evidence instead of rerunning blindly. RcloneView also syncs and compares folders, with basic sync and folder comparison available on the FREE license.
Manage & Sync All Clouds in One Place
RcloneView is a cross-platform GUI for rclone. Compare folders, transfer or sync files, and automate multi-cloud workflows with a clean, visual interface.
- One-click jobs: Copy · Sync · Compare
- Schedulers & history for reliable automation
- Works with Google Drive, OneDrive, Dropbox, S3, WebDAV, SFTP and more
Free core features. Plus automations available.
Confirm the Remote Still Connects
If a job fails within seconds, suspect the remote before the data. Open Remote Manager from the Remote tab, edit the Files.com remote, and re-enter the credentials if they have changed or expired. Then open the remote in an Explorer panel and browse the root folder. If it lists normally, the connection is healthy and the problem lies elsewhere.
In the built-in Terminal tab you can also run rclone about "remote:", replacing remote with your remote's name, as a quick check that the account responds.
Read Job History and Turn On DEBUG Logging
Open Job History and check the status, duration, and file count of the failed run. A job that errors partway through usually points to specific files or transfer load, not credentials.
For the exact message per file, go to Settings > Embedded Rclone, enable rclone logging, set the level to DEBUG, and click Restart Embedded Rclone. Reproduce the failure and read the log in the Log tab or in your configured log folder.
Lower Concurrency and Preview the Rerun
Intermittent failures often ease when fewer files move at once. In Step 2 of the sync wizard, reduce the number of file transfers and set equality checkers to 4 or less, which is the guidance for slow backends. Keep "Retry entire sync if fails" at 3 so transient failures are retried up to three times.
Before rerunning, use Dry Run to review which files will be copied or deleted, so the retry cannot surprise you.
Verify With Folder Compare
After the rerun, open Compare with your local folder on one side and Files.com on the other. Filter for left-only, right-only, and different files to see what is still missing or mismatched, then copy just those items instead of repeating the entire job.
Getting Started
- Download RcloneView from rcloneview.com.
- Re-check the Files.com remote in Remote Manager and confirm the root folder lists.
- Check Job History and enable DEBUG logging for the failing job.
- Lower concurrency, run a Dry Run, rerun, and confirm the result with Folder Compare.
Once the cause is visible in the logs and the comparison, a Files.com failure becomes a short, repeatable fix.
Related Guides:
- Manage Files.com Storage — Sync and Backup Files with RcloneView
- Fix SugarSync Sync Errors with RcloneView
- Log and Debug Cloud Transfers — Troubleshoot Issues in RcloneView
Supported Cloud Providers
