Fix Jottacloud Sync Errors — Troubleshoot and Resolve with RcloneView
When a Jottacloud sync job stalls, errors out, or silently skips files, the fix is usually in the job's advanced settings, not the provider itself. RcloneView gives you the visibility to find and correct it.
Jottacloud is a Norwegian cloud storage provider with strong privacy guarantees, and RcloneView connects to it directly for browsing, syncing, and backup. Sync errors with Jottacloud tend to fall into a few recurring patterns: authentication drops, transfers that hang partway through, and mismatched files after a run completes. Because RcloneView surfaces detailed job logs and lets you adjust transfer settings per job, most of these issues can be isolated and resolved without leaving the app.
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.
Diagnosing the Failure with Job History and Logs
Before changing any settings, check what actually happened. Job History records the execution type, status (Completed / Errored / Canceled), total size transferred, and duration for every run — this immediately tells you whether a job failed outright or completed with partial results. For deeper detail, enable rclone logging in Settings, set the log level to DEBUG, and restart the embedded rclone connection before reproducing the sync. The resulting log file shows the exact API response Jottacloud returned, which is far more useful than a generic "sync failed" message.
Fixing Stalled or Hanging Transfers
If a Jottacloud job appears to hang partway through with no progress in the Transferring tab, the most common cause is too many concurrent connections overwhelming the provider's API. Lower the number of file transfers and multi-thread transfers in the sync job's Advanced Settings step — Jottacloud handles a smaller number of concurrent streams more reliably than providers with higher API tolerances. Reducing the number of equality checkers to 4 or fewer is also recommended for slower backends, which cuts down on the parallel comparison requests that can trigger throttling.
Catching Mismatches Before They Become Data Loss
Sync errors aren't always loud failures — sometimes a job completes but leaves files out of sync due to timestamp or checksum discrepancies. Running a Dry Run before the real sync shows exactly which files will be copied or deleted, letting you catch unexpected changes before they happen. If files consistently show as different despite matching content, enabling the checksum comparison option forces RcloneView to compare files by hash and size rather than modification time, which resolves most false-mismatch cases. RcloneView mounts AND syncs 90+ providers from one window, so you can cross-check a suspect file's actual size directly in the Explorer panel before troubleshooting further.
Retry settings also matter here: leaving "Retry entire sync if fails" at its default of 3 gives transient Jottacloud connection blips a chance to resolve automatically before you need to intervene manually.
Getting Started
- Download RcloneView from rcloneview.com.
- Open Job History for the failing Jottacloud job and note the exact status and error.
- Enable DEBUG logging and reproduce the sync to capture the specific API response.
- Adjust concurrent transfer and checker counts, then re-run with a Dry Run first.
A few targeted adjustments in the sync settings resolve the vast majority of Jottacloud sync issues, keeping your backups reliable without guesswork.
Related Guides:
- Manage Jottacloud Storage — Sync and Backup Files with RcloneView
- Fix Nextcloud Sync Errors — How to Resolve with RcloneView
- Dry Run — Preview Cloud Sync Before Transfer in RcloneView
Supported Cloud Providers
