I think the reason why the workaround didn’t work on your end is because the &access_type=offline is added to http://connect.insynchq.com/auth?cloud=gd, instead of the URL of the page that gets shown afterwards.
Looking back, we also found the workaround we provided a bit confusing and hard to follow, apologies on that. Here’s the updated and simpler version (no copy-pasting and modification needed):
@daryll, what if I have three (3) instances of Insync Headless running under different Linux users, but all using that same Google Drive? Each is synchronizing a different sub-set of data (folders) in that Google Drive. Will that special link you provided work three (3) times? or just once?
@daryll After trying to add the account back into Insync Headless using the link you provided to generate the auth code, it does not successfully add the account. Nor does it throw any kind of (visible) error. If I do “insync-headless status” it says:
insync-headless status;
No accounts added yet. See insync-headless account add --help.
UPDATE/CORRECTION: It took several minutes, and then started showing-up under “insync-headless status”.
After the account seemed to add successfully, it immediately throw errors again. In response to “insync-headless error list”, to showed this (now very familiar) prompt:
insync-headless error list;
1 - Your authentication token has expired. Please try logging in again.
Choose an error to resolve (1 - 1, 0 to quit): 1
1 - Login
Choose an option (1 - 1, 0 to cancel): 1
So, same symptoms as with the other link/process. Monitoring now to see if it is really synchronizing again (after responding to that re-login prompt), or just enumerating all the (tons of) files already there in the folder.
The good: Hasn’t thrown the error about the authentication token again (yet).
The bad: Status is still “SYNCING”. So, will continue to monitor to see if it completes or errors-out again.
PS: Have not (yet) tried setting-up the additional instances, just running Insync Headless under one Linux user at the moment. After the current sync finishes (or errors out again), will try the additional instances.
Got tired of waiting for the first Insync Headless instance to complete, so I went-ahead and setup the other two (2) similarly (using the special link provided to generate the auth code, etc.)
Rough size and count of files involved for perspective:
Approximately 3935 files, spread over 78 folders, representing about 27.5-GB of data.
Approximately 18314 files, spread over 916 folders, representing about 18-GB of data.
Approximately 49 files, spread over 7 folders, representing about 795-MB of data.
Here’s where things are currently at:
The largest one I started first, and has been running for over 24-hours - still not “completed” (to “SYNCED” status, etc.).
The second one is the 2nd largest, and is similar situation but with some extra errors (noted further below).
The third one is the smallest and generally synchronizes very quickly even if zero data was already present on local disk. Similarly, it is stuck in an forever “SYNCHRONIZING” state, never completing.
Regard the “extra” errors on the 2nd one:
It originally complained about some symbolic links not synchronizing, which I already dismissed (with insync-headless error dismiss-all). But, sometimes those exact errors show up again, and have to be dismissed again. I say the same errors, because its for the same exact symbolic links - not another different set of symbolic links.
Now it permanently says “ERROR” but no errors show-up (using either insync-headless error list -nor- insync-headless conflict list).
Hello! Thank you so much for the detailed walk-through of what has happened in the last few days, and my sincerest apologies for the continued troubles.
For the 2nd and 3rd setups, could you also please send me the latest set of log files namely:
logs.db
out.txt
data folder
live folder
Please do send them once more to support@insynchq.com with the link to this post.
Thanks for sending us the logs. Upon checking them, instances 2 and 3 are still running into the authentication token issue.
Just to confirm, were you able to perform the step below before clicking on the link? This is a necessary prerequisite to fix the issue with the non-refreshing token.
I tried last instructions and did not work for me.
With the authorization token received in step 3 (I did the first two without issues), I tried to add the account using insync-headless but received the following message:
Yes, removed the account from all three instances of Insync-Headless.
Then, removed Insync from Google Account permissions.
When I re-added the first account, I used the special link.
It said it successfully added the account, but within minutes it threw the error about logging-in again (which I did).
After that the status stayed “SYNCING” - never completing. Never changing to “SYNCED”.
Later, I re-added the account to the other two (2nd and 3rd) instances - also generating the auth code with the special link provided. The did not immediately prompt for re-login, but also are stuck “SYNCING” - forever (including the smallest one). However, later (today) the 2nd did prompt for re-login (which I did). So far, the 3rd has not thrown that error again (yet).
Obviously, I did NOT remove the Insync permissions between adding the 1st instance and adding the 2nd and 3rd instances - as that would presumably break the authentication for the 1st instance?.
In the Google Account, its NOT like it shows-up as three separate applications - its all just “Insync”.
@Mecha_Weasel@maicmarin May we ask you to please try again, this time with the three steps above? As per our Linux Team, they have already deployed a fix to web and have confirmed the steps to be working on their end. Thank you very much!
