Skip to main content

Fix premiumize.me Sync Errors — Authorization and Transfer Problems Resolved with RcloneView

· 3 min read
Casey
Product Manager

When a premiumize.me job fails, RcloneView's job history, DEBUG logs, and Folder Compare show whether the cause is the login, the transfer load, or files that never arrived.

A premiumize.me job that stops early, or leaves a folder half copied, is hard to diagnose from a bare command line. RcloneView keeps the remote check, the job record, the log, and a side-by-side comparison in one window, so you can fix the real cause instead of rerunning blindly. RcloneView mounts AND syncs 90+ providers from one window, on Windows, macOS, and Linux.

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.

Re-Authorize the Remote​

premiumize.me connects through OAuth in the browser. If jobs fail within seconds, the login is the first suspect. Open Remote Manager from the Remote tab, edit the premiumize.me remote, and sign in again through the browser prompt.

Then open the remote in an Explorer panel and browse the root folder. If it lists normally, the connection is healthy and the failure lies in the transfer itself.

Re-authorizing a premiumize.me remote in RcloneView

Read Job History and Enable DEBUG Logs​

Open Job History and check the status, duration, and file count of the failed run. A job that errors midway usually points to particular files or to load, not credentials.

For the exact per-file message, go to Settings > Embedded Rclone, enable rclone logging, set the level to DEBUG, and click Restart Embedded Rclone. Reproduce the failure, then read the Log tab or the log file in your configured folder.

RcloneView job history showing an errored premiumize.me job

Reduce Load and Preview the Rerun​

Intermittent failures often ease with fewer simultaneous transfers. In Step 2 of the sync wizard, lower the number of file transfers and set equality checkers to 4 or less. Keep "Retry entire sync if fails" at 3 so transient errors are retried.

Before the rerun, use Dry Run to see which files would be copied or deleted, so the retry holds no surprises.

Re-running a premiumize.me job with lower concurrency

Confirm With Folder Compare​

After the rerun, open Compare with a local folder on one side and premiumize.me on the other. Filter for left-only, right-only, and different files, then copy only what is still missing rather than repeating the whole job.

Folder Compare showing files missing on premiumize.me

Getting Started​

  1. Download RcloneView from rcloneview.com.
  2. Re-authorize the premiumize.me remote and confirm the root folder lists.
  3. Check Job History and turn on DEBUG logging for the failing job.
  4. Lower concurrency, run a Dry Run, rerun, and verify with Folder Compare.

With the cause visible in logs and comparison, a premiumize.me failure becomes a short, repeatable 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