OS: Debian 10 “Buster” (64-bit) - planning to upgrade soon to Debian 11 “Bullseye” btw.
Product: Insync Headless for Linux (3.2.7.10758)
Utilization:
One Linux server.
Multiple copies of Insync Headless running.
Each running under different Linux user.
All synchronizing different sets of sub-folders from the same Google One Drive account.
Obviously, different authentication tokens generated used for each Headless instance (each Linux user). - since (presumably) those authentication tokens can only be used once.
This all worked fine previously.
Got everything setup, was running fine for a while, then start getting messages like this:
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
The zip-files I made containing that information for each account are too large to email (100-MB to 300-MB each). So sending my DropBox link in the email.
PS: None of the 3 instances are currently throwing the “expiration” error, but 2 of the 3 are still in a “scanning” state.
Hey there! Could you try to do the following, please?
Remove the affected account
Under Google Account > Apps with access to your account, click on Insync and select remove access.
Do the headless login flow afterwards–
When you get redirected after step 1 in the headless add account flow, you need to copy and modify the URL. Here are the steps in detail:
Modify the URL by adding the following at the end:
&access_type=offline
3. Browse to the modified URL and login using the selected account. Proceed with the normal headless add account flow.
While I appreciate the fast response. deleting the account and basically starting over (including re-syncing all my data and dependencies) on a production server, isn’t really something I want to “try” as a troubleshooting step.
If it is the known/documented (one-time) permanent fix, then so be-it. But “try” - Not so much so.
I understand the apprehensions to give the workaround a try, @Mecha_Weasel. You may hold off doing so until I get more information on the issue (both from users and our engineers) as we have received mixed results from said workaround.
As for the logs, if it’s possible for you to upload them in the cloud (i.e., WeTransfer) and send me a shared link to download, that would be much appreciated!
I might get a chance today/tomorrow to take the system down for some unrelated maintenance.
If so, I will try the work-around, since 2 of the 3 instances are not actually synchronizing anyway.
Is there any new version of insync-headless I should think about trying? or still headless_3.2.7.10758?
Trying the work-around (http://connect.insynchq.com/auth?cloud=gd&access_type=offline and so-forth) right now. Two (2) of three (3) instances (the large ones) are showing “scanning” status afterwards. I will monitor them, and see if they eventually complete, or throw the token expiration error again.
PS: I noticed that the insync-headless account help page still shows the older authentication URL to use (without cloud type specified), as opposed to the help page output for insync-headless account add.
Commands:
add Add an account via auth code from https://connect.insynchq.com/auth.
list List existing accounts.
remove Remove an account.
Output of insync-headless account add …
Usage: insync-headless account add [OPTIONS]
Options:
-a, --auth-code TEXT Auth code received from signing in at https: //connect.insynchq.com/auth?cloud=
-c, --cloud [gd|od|dx] Cloud provider to add the account for:
Google Drive (gd) / OneDrive (od) / Dropbox
(dx).
-p, --path TEXT Path to sync your files to.
-e, --export-option [LINK|MS_OFFICE|OPEN_DOCUMENT]
Export option for Google-format items.
–help Show this message and exit.
Oddly enough, two (2) of the three (3) instances are fully “SYNCED”.
And those are the very large ones (both in terms of number of files and total size to synchronize).
The one (1) instance that still shows “SYNCING” hour+later is the tiny one.
As it so happens, it was the third one I setup.
I am wondering if Google has placed some limitation how many instances of the same application (“Insync” as far as Google is concerned) can be activated? Maybe limiting it to two or something?
Update: On that third instance (the one with the least files and data, but was 3rd one activated), It just threw the error again - requiring selecting the option to login again:
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
Update-2: At this point all three (3) instances have thrown the same error requiring re-login. So, the work-around definitely does not “work” unfortunately.
Thank you all for the information you shared and my apologies for the persistent issues.
@Mecha_Weasel@maicmarin Please do send a fresh set of log files (logs.db and out.txt) for each machine showing the issue. Kindly forward these files to support@insynchq.com with the link to this post. Thank you very much!