Your authentication token has expired. Please try logging in again [under investigation]

Bugs and issues Linux
#21

@mia mail with logs sent.

Thanks,

1 Like
#22

Thank you @abadr! I have received them :slight_smile:

#23

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

#24

@mia I’m afraid this new version didn’t solve the problem.

ash_20230329_221946
ash_20230329_221946750×453 22.9 KB

#25

@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.

#26

@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!

#27

The same issue here.

1 Like
#28

@mia, Eureka, it works … for now. I will confirm if this works long term since previously it worked for an hour or two with the alternative login and disconnects again. But now it works with the standard login link which it didn’t do before.

I found the culprit at least in my case: Frustrated with this issue I tried to setup Rclone to do the syncing job but I got the same “Something went wrong” authentication error while authenticating Rclone to Drive. Realizing that the problem is not unique to Insync, I tried the Insync authentication link using a fresh install of the Brave browser and it worked like a charm first time.

I was using Firefox with “Standard Tracking Protection” enabled and a bunch of privacy extensions. Apparently one of those extensions screwed things up. Or maybe the Drive authentication system only plays nice with the chrome engine. I didn’t do any granular testing to find out the culprit.

Hope this helps other users.

2 Likes
#29

My environments (where it definitely is still not working):

Server:

  • Debian 10
  • Insync Server/“headless” v3.2.7.10758

Client:

  • Windows 11 Pro (with latest updates).
  • Google Chrome (latest version)
  • Google account with “Google One” storage upgrade.
#30

Hi @Ehsan_Akrami, what’s your Insync version please?

#31

Hi Mia,
I am using headless version 3.2.7.10758

1 Like
#32

Gotcha. May I confirm if you’ve already tried the proposed workaround?

  1. Remove the affected account
  2. Under Google Account > Apps with access to your account, click on Insync and select remove access.
  3. Do the headless login flow afterwards.