Hello everyone! We are working on resolving this top priority issue as soon as possible. @Marbot Could you please send your logs.db and out.txt files to support@insynchq.com after quitting Insync?
Those 2 files should be in ~/.config/Insync. Thank you!
I hope they do get a robust headless implementation working. Though rclone will do the job, it is not a synchronization tool in the sense that you are cloning from or to a remote repository (though there is a sync option). It’s implementation is a bit more “you manage it” or automate it via shell scripts with your workflow (backups or file processing etc).
I can confirm i have the same error - running headless on debian
Hey everyone!
Are there any updates on this? I’m currently evaluating Insync for our company, but this issue is basically rendering it unusable. I’d gladly try some beta builds as well, because apart from this issue Insync looks really promising.
Hi,
I’m also having this problem on a new install openSUSE Tumbleweed. I have 2 other computers with old installs with the same OS and Insync versions and they works fine.
Insync desktop v 3.8.4 50481
Any help is appreciated, this issue is causing some major productivity problems.
Thanks
Hello everyone! We’d like to ask the affected Desktop users to please follow these steps as a temporary workaround while we continue to work on the fix:
&access_type=offline to the URL, like so:
https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=468017360789-e4camv9a5n4e90tk4vrpk49qonmcm95s.apps.googleusercontent.com&redirect_uri=https%3A%2F%2Fconnect.insynchq.com%2Fauth-login&scope=openid+email+profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fdrive+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fdrive.appdata&access_type=offline
@mia, thanks for the workaround, however I’m not willing to remove access from Google as Insync is running on 2 other computer and I’m afraid If I remove access I will not be able to login using those computers as well.
Is there a way around this?
Thanks
Same problems here. Everything works 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
My environment:
Hi @Mecha_Weasel,
I appreciate that you tried the workaround. Could you send me your latest set of logs.db and out.txt files please? You may email them to support@insynchq.com 
Thank you!
yes did that.(i.e. sent the logs to support)
Yes @mia , I have 2 computers with old Insync installs that are running fine. I’m worried that if de-authenticate those computer I’d have the same problem with them as well. It’s the 3rd “new” computer that I’m having problems with. All computers are running openSUSE Tumbleweed and are updated daily. They also all run the same Insync version 3.8.4.50481.
@abadr I see! Thank you for sharing this important detail. Allow me to inquire with our engineers regarding this first. Could you email support@insynchq.com the log files from each computer? Please include the following:
If they’re too big as an email attachment, you may upload them to the cloud and send me a shared link to download.
Hi @abadr,
Could you try 3.8.5 for that “new” computer and let me know if the authentication issue persists? The build can be tested from here: New Insync version: 3.8.5
@mia I just wanted to add to the conversation that this issue appears to occur when trying to sync with a Microsoft OneDrive account as well. I have a fresh install (after a hard drive failure). I am syncing with a OneDrive account but am receiving the same error message and syncing does not occur.
@jfleck Hi Jeremy, could you send your logs.db and out.txt files to support@insynchq.com with the link to this post? I will check and see what the OneDrive equivalent is for the solution above.
Thank you!
