Cloud sync troubleshooting
What to do when the Google Drive sync misbehaves. Setting the sync up in the first place is Google Drive session sync, and the section numbers referred to below are that page’s.
Troubleshooting quick reference
| Symptom | Likely cause | Fix |
|---|---|---|
| Wizard tries to open a browser / hangs on a Pi | answered “yes” to auto config | Re-run, answer No, use rclone authorize on a desktop (Section 5) |
| Sync works for ~7 days then stops | OAuth consent screen left in Testing | Publish App (Section 1, step 3) and re-auth |
Frequent rateLimitExceeded / slow sync |
using rclone’s shared default client ID | create your own OAuth client (Section 1) |
| Peer IO view empty, no error | peer never pushed yet | wait one push cycle; confirm with Section 8 |
| Section 8 listing errors with permission/not-found | sign-in model wired wrongly | shared account: confirm both Pis signed in as the same account; service accounts: confirm mseq/ is shared with each (Section 9, step 4) |
Cross-References
- Google Drive session sync: the setup walkthrough these fixes refer back to
- Saving and loading sessions: what the sync does once it is running