Google API dailyLimitExceededUnreg Error

Hello! I was using Insync for years without problems, recommending its use to many customers.

Unfortunately I decided to upgrade from version 1.5 to version 3 a few days ago, from that moment a series of errors and huge problems began, such as hours, tens of hours, of CPU intensive use and not synchronization, abrupt closures of the application, for some reason re-uploads of thousands and thousands of files already synchronized to Google Drive, in some cases duplicating the files and folders, in others stepping on the original editing / creation time for the current one, etc.

After all these problems, I decided to revert the version back to 1.5, but apparently the GUI with ubuntu 19.10 no longer works, giving segfaults apparently due to conflicts with gnome, xorg, etc., so I decided to try again with version 3.

After hours of trying to synchronize (there really is nothing to synchronize, maybe 1 or 2 files, since everything was really synchronized), and several minutes of re-uploads of files to drive, I see in the file out.txt many entries of error related to “Daily limits Exceeded” and CurlError due to this.

There are many Curl error entries pointing to error urls with the following content:

{"error":{"errors":[{"domain":"usageLimits","reason":"dailyLimitExceededUnreg","message":"Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup.","extendedHelp":"https://code.google.com/apis/console"}],"code":403,"message":"Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup."}}

Do you know how I could fix this? I fear anyway that by correcting the excess of daily connections, Insync continue rewriting all the online content (locally near 100GB).

Thank you,
Daniel

@dannet Migrating from 1.5 to 3 for a large dataset may take quite some time and may cause rateLimitExceeded errors for the account but we haven’t come across dailyLimitExceededUnreg error. Also, it shouldn’t re-upload a whole lot of files unless the local copies are really different from the cloud ones.

Could you send the Insync logs to support@insynchq.com so that we could look into this?