Skip to main content

Fix Cloud Transfer Stalled Progress — How to Resolve with RcloneView

· 4 min read
Tayson
Senior Engineer

A transfer showing 99% for hours signals a specific underlying problem — RcloneView gives you the monitoring and control tools to diagnose the stall and restart cleanly without data loss.

A cloud transfer that freezes near completion, or a sync job that runs indefinitely without finishing, is one of the most disruptive cloud management problems. Stalled transfers typically result from large files hitting API timeout limits, network interruptions that rclone's retry logic doesn't recover from, or provider-side throttling that causes connections to hang. RcloneView surfaces what's happening and lets you intervene precisely.

RcloneView app preview

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
WindowsmacOSLinux
Get Started Free →

Free core features. Plus automations available.

Diagnosing the Stall

Open RcloneView's Transferring tab in the bottom Info View. This panel shows active jobs with real-time progress: transfer speed, file count, and the specific file currently being processed. A stall is immediately visible here — the speed drops to 0 B/s while a specific file shows no progress change.

RcloneView Transferring tab showing a stalled cloud transfer

Switch to the Log tab for error messages. Common stall causes appear here with timestamps:

  • "too many requests" — API rate limiting is throttling the transfer
  • "connection reset by peer" — a network interruption broke the active session
  • "EOF" or timeout messages — the provider closed the connection during a large file upload

For very large files (multi-GB video files, database dumps), the issue is often a session timeout on the provider's end during multipart upload assembly. The upload completes but the provider's session expires before it acknowledges the completed parts, causing rclone to wait indefinitely.

Recovering a Stalled Transfer

Cancel the stalled job by clicking Cancel on the active job in the Transferring tab. RcloneView's sync and copy jobs are designed for safe restart — when you run the same job again, rclone compares what already exists at the destination and skips files that transferred successfully. Only the stalled file (and anything that hadn't started) will be retried.

Canceling and restarting a stalled transfer job in RcloneView

For persistent stalls on specific large files to S3-compatible backends, increase the chunk size in RcloneView's global rclone flags (Settings > Embedded Rclone > Global Rclone Flags): add --s3-chunk-size 256M to reduce the total number of API calls required for large file assembly.

Preventing Future Stalls

Set the retry count in Job settings (Step 2: Advanced Settings > Retry entire sync if fails) to 3 or higher — this ensures transient network issues trigger automatic retries rather than immediate job failure. For transfers over slow or unstable connections (VPN, mobile hotspot), reducing the Number of file transfers (concurrent transfers) reduces contention on the link.

Job history showing recovered transfers after stall resolution in RcloneView

The Job History tab shows patterns over time — if the same job stalls consistently at a particular time of day, the cause is likely provider-side rate limiting during peak hours. Adjusting your schedule to off-peak times resolves this without any configuration changes.

Getting Started

  1. Monitor transfers in the Transferring tab — look for 0 B/s speed on a specific file.
  2. Check the Log tab for error messages indicating the root cause (timeout, rate limit, network reset).
  3. Cancel and restart the job — rclone resumes from where it stopped, skipping completed files.
  4. Increase retry count and adjust chunk size in Advanced Settings to prevent future stalls.

Stalled transfers are almost always recoverable — the key is identifying whether the cause is provider-side, network-side, or configuration-related, then applying the targeted fix.


Related Guides:

Supported Cloud Providers

Local Files
WebDAV
FTP
SFTP
HTTP
SMB / CIFS
Google Drive
Google Photos
Google Cloud Storage
OneDrive
Dropbox
Box
MS Azure Blob
MS File Storage
S3 Compatible
Amazon S3
pCloud
Wasabi
Mega
Backblaze B2
Cloudflare R2
Alibaba OSS
Ceph
Swift (OpenStack)
IBM Cloud Object Storage
Oracle Cloud Object Storage
IDrive e2
MinIO
Storj
DigitalOcean Spaces