Fix OAuth Token Expired Errors — Re-authorize Cloud Accounts in RcloneView
Your nightly backup has been failing silently for two weeks. The error: "token expired." Your Google Drive, OneDrive, or Dropbox connection just needs a re-authorization — here's how to fix it.
OAuth tokens connect RcloneView to cloud providers like Google Drive, OneDrive, Dropbox, and Box. These tokens have expiration policies — Google tokens last indefinitely but can be revoked, Microsoft tokens expire if unused for 90 days, and password changes or security events invalidate all tokens. When they expire, sync jobs fail silently until you notice.
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.
Common Token Expiration Causes
| Provider | Token Behavior |
|---|---|
| Google Drive | Refresh token valid until revoked (but can be revoked by user or admin) |
| OneDrive | 90 days if not used; password change invalidates |
| Dropbox | Valid until explicitly revoked |
| Box | 60 days without refresh |
Symptoms
- Scheduled jobs fail with "authentication" or "token" errors
- Manual browsing shows "unauthorized" messages
- Job history shows increasing failures over recent days
How to Fix
Check job history first
Look for patterns — if all jobs for one provider started failing on the same date, it's a token issue.
Re-authorize the remote
Open the remote manager and re-authorize the affected remote. This triggers a new OAuth flow — sign in to the provider and grant access again.
Your existing job configurations are preserved. Only the authentication token updates.
Verify the fix
Run a test sync to confirm the connection works:
Prevention
- Enable notifications — Slack/Discord/Telegram alerts tell you immediately when a job fails
- Check job history weekly — catch failures before they accumulate
- Avoid password changes without re-authorizing cloud remotes
- Use service accounts for Google Workspace (they don't expire like user tokens)
Getting Started
- Download RcloneView from rcloneview.com.
- Check job history for auth-related failures.
- Re-authorize affected remotes in the remote manager.
- Set up notifications to catch future failures early.
A 2-minute re-authorization prevents weeks of missed backups.
Related Guides:
Supported Cloud Providers
