I have the same issue. After a couple of minutes of synchronising data i receive the message ‘Your authentication token is invalid’.
I need to login again every few minutes which is pretty annoying.
Running version 3.2.0.40833 on Ubuntu 20.04.
Clearing browser data did not help!
Hey guys! Sorry about this-- we’re looking into the issue and what’s causing this to keep popping up.
Please send your logs.db and out.txt files to support@insynchq.com with the link to this post. Thank you!
I am seeing this on Linux (Fedora 32) as well.
I’m also seeing this in Ubuntu 18.04 for OneDrive
Unfortunately updating to the latest version (v3.2.1.40839) didn’t make a difference. I have noticed, file changes are in fact being synced, but only when the application is running for a few minutes…
same problem here. I have tried change password/ revoke permissions in office account etc…
Any updates on this, looks like many people are having this issue… I haven’t be able to sync my files for almost a month now… @mia
Hey guys! So sorry for the trouble. We’re including better logging info on the next release to help us troubleshoot this further.
I’ll link it here when it’s out with further instructions.
Same problem here. I’m seeing this on PopOS 20.04
Hi all! 3.2.2 is available here: New Insync version: 3.2.2
To update, please do the following:
As soon as you see the pop-up message re: authentication token invalid:
Thank you!
I recently enabled MFA (Multi-Factor-Authentication or 2FA) on my Microsoft 365 account.
This caused me to have to re-auth with all my connected devices.
However I get the “Your authentication token has expired. Please try logging in again.” error with Insync.
When I goto Help => Alternative Login and paste the OneDrive URL into a browser and Authenticate with Microsoft I get a blank page and no code to enter into Step 2 of the alternative login.
I have sent my out.txt and logs.db to support@insynchq.com but strangely there wasn’t even an auto-reply.
Seems to be a problem with their authentication end-points, as well as the app.
app_version=3.2.4.40856, platform=Linux-x86_64-fedora/32
Support got back to me. And the following worked for me.
Log back in!
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.
Hi guys! For those who are experiencing an expired token issue on the latest version (3.2.7), please shoot us an email at support@insynchq.com-- we have an alpha build that we can send for testing before we roll it out.
So far, a couple of users have already confirmed the fix-- would love for you guys to try it out as well.
Thanks!
I am on 3.2.7.40868 (Linux Mint) and so far no issues
Ubuntu 20.10 Insync 3.3.4.40916
“your authentication token is invalid” : I have to login +/- 3 times a day, I don’t know why
Hi! Can you send your logs.db and out.txt files? These are in ~/.config/Insync. Please email them to support@insynchq.com 
Similar problem here.
“Your authentication token is invalid…”
Started some days ago and the number of messages per day is growing.
I then log in, it works for a while and after some hours the message is back.
Every help highly appreciated.
TIA
Peter
@Peter_William_LeMans Hello! So sorry for the trouble you’re facing.
Could you please send the following to support@insynchq.com:
Here’s how to find those logs: https://help.insynchq.com/en/articles/1834816-locating-the-log-files
Please let me know as well if you tried logging in via normal login (like adding a new account) or via the alternative login method.
I’m facing the very same problem here with Google Drive.
Very annoying.
Hi @Carlos_A_Rocha_Rodri! Just in case you have not, please do follow the instructions below to send your log files.
Email the following to support@insynchq.com after Insync is closed:
These two files can be found by following the instructions here: https://help.insynchq.com/en/articles/1834816-locating-the-log-files. Please also include the link to this Forums post so I can trace the original report accordingly.
Thank you!