Skip to content

Cloud Sync Troubleshooting

This page covers common Cloud Sync issues and how to resolve them.

Symptom: Data is not syncing between devices.

Solutions:

  1. Check internet connection: Cloud Sync requires an active internet connection on all devices.
  2. Verify subscription: Confirm your Cloud Sync tier is active in Settings > Cloud Sync.
  3. Force sync: Go to Settings > Cloud Sync and tap Sync Now to trigger a manual sync.
  4. Check all devices use the same account: Ensure you are signed into the same sync account on all devices.

Symptom: “Incorrect password” when trying to sync.

Solutions:

  1. Check for typos: The sync password is case-sensitive.
  2. Use your recovery key: If you have forgotten your sync password, use the recovery key to reset it. Go to the sync login screen and select Recover with Recovery Key.
  3. Password was changed on another device: If you changed your sync password on one device, use the new password on all other devices.

Symptom: Data appears different on different devices after syncing.

How ZestSSH handles conflicts:

Cloud Sync uses timestamp-based conflict resolution. When the same item is modified on two devices while offline, the most recent change takes precedence when both devices sync.

If you lost data due to a conflict:

  1. Check if the lost data is in a local auto-backup (ZestSSH keeps up to 3).
  2. Restore the specific items from the auto-backup if needed.

Symptom: You cannot find your recovery key and have forgotten your sync password.

Unfortunately, without either your sync password or recovery key, your synced data cannot be decrypted. This is the nature of zero-knowledge encryption.

What you can do:

  1. Reset Cloud Sync and start fresh with a new password.
  2. Restore data from a local encrypted backup if available.
  3. Re-create connections manually if no backup exists.
  4. Going forward, store your recovery key in a password manager.

Symptom: Sync takes a long time to complete.

Solutions:

  1. Check your internet connection speed.
  2. Sync large datasets (many connections, keys) may take longer on first sync.
  3. Subsequent syncs are incremental and should be faster.