INITIALIZATION FAILED

The Initialization Failed error is usually caused by a corrupt database. In most cases, this can be resolved by removing and re-adding the affected account to the Insync app:

  1. Remove your account from Insync.
  2. Add it again to the app (this will take you to initial setup and will sync afresh).
  3. During setup, you may select your existing Base Folder (make sure to select the correct folder) so there would be no need to upload or download.

Warning: Note that removing your account from the app will erase your custom selective sync location settings and ignore rules. You’ll need to set them up again upon logging in.

CONNECTING TO INSYNC

Once you have authenticated your Google Account, your browser will say "Connecting to Insync...". In case it gets stuck, try these steps:

  1. Uninstall your Insync app.
  2. Re-install the latest version.
  3. Do the alternative login method.

Still not working?

  1. Check if you are behind a proxy or using a firewall.
  2. If you're on a OneDrive school account, send the web URL of the “Connecting to Insync…” page to support@insynchq.com so we can take a better look.

CHANGING BASE FOLDERS

Are you trying to change your Base Folder via the app setting but it keeps getting reverted to the default location? Try these steps, but do note that it will ask you to sync afresh:

  1. Close the app
  2. Delete your user/data files found along with your logs.
  3. Reboot the app
  4. Change the Base Folder location.

STUCK SYNCING

The most common symptom shows “Syncing…” at the bottom of the UI with an “Uploading 0 of X bytes”. Others see the blue circle beside their files with no visible progress. This issue is being investigated by our engineers. Please send the following to support@insynchq.com:

  • Logs.db
  • Out.txt
  • Data folder
  • Live folder

If they’re too big as an attachment, please send us a link to download.

ERROR MESSAGES

Unexpected error doing ModifyLocalReg: error code 503

Are you using OneNote? If so:

  1. Try to save your changes on OneNote and restart Insync.
  2. If the error is still present, click RETRY.

Update: This is an issue in progress and will be addressed in an upcoming build.

Unexpected error doing ModifLocalGDReg: 500: Internal Server Error

It seems like Google fixed this error on their end.

  1. Try to dismiss or retry those errors if they're still in the Attention Required.
  2. Another way to clear them (if retry doesn't work) is to open the file in Google web editor and make a few changes so it syncs back to your computer.

Cannot add [file] directly to Shared base folder

You cannot add a normal file or folder locally to the root of your Shared Drives Base Folder because it does not behave like a Shared Drive. Please remove this file/folder to clear the error and move it to its appropriate directory.

Unexpected error doing AddCloudGDItem: (28, 'Operation too slow. Less than 1 bytes/sec transferred the last 40 seconds')

This is possibly caused by a large transfer that caused a delay in the network. Try to restart Insync. If restarting doesn't work, please reinstall Insync.

AddCloudODItem: invalidRequest: The provided name cannot contain leading, or trailing, spaces.

This is a OneDrive limitation wherein extra spaces at the start of the filename is now allowed.

  1. Remove the extra space at the start of the file name.
  2. Click RETRY on the error message.

AddLocalGDItem: 'NoneType' object has no attribute 'startswith'

  1. Check if you're on the latest version. This was addressed in 3.1.9.
  2. If not, quit Insync.
  3. Install the latest build from our downloads page.

Unexpected error CurlError: (77, ‘error setting certificate verify locations:\n CAfile:/etc/ssl/certs/ca-certificates.crt\n CApath: none’)

If you’re on Linux, run the following commands, then restart Insync:

  1. apt-get autoremove ca-certificates
  2. apt-get install ca-certificates

--------------------------------------------------

Email support@insynchq.com if 1) the issue persists or 2) you have a bug not listed here. Please include the following files for investigation:

  • Logs.db
  • Out.txt
  • Data folder
  • Live folder
  • Steps that led you to this error
  • Screenshots if applicable
  • Link to your Insync Forums post/comment if applicable
Did this answer your question?