Hi everyone,
I'm running into a persistent login issue with Loom and hoping someone has experienced the same or found a fix.
Every time I try to sign in using Google, I'm immediately redirected back with the following error:
"Could not authenticate with Google, please try again. If the issue persists reach out to an admin or the Loom support team."
The URL at that point looks like:loom.com/oauth-callback?oauth_error=Could+not+authenticate+with+Google...&provider=google-authentication&login_success=false
Because of this, I'm completely locked out of my account — I can't access the Library, my recordings, or the in-app support form.
What I've already tried:
Logging in across multiple browsers
Clearing cookies and cache
Trying incognito/private mode
My setup:
Login method: Google (OAuth)
Account email: hi@samstoof.com
Location: Netherlands
Has anyone encountered this and resolved it? Is this a known issue on Loom's end, or something tied to Google's OAuth configuration? Any help is appreciated.
Thanks in advance,
Sam
Hello @Sam Stoof
Good advice from @Ajay _view26_ .
Just to add one practical thing: since you're locked out and can't access the in-app support form, you can reach Loom/Atlassian support directly at support.atlassian.com without needing to be logged in to Loom. That's your fastest path to getting this resolved at the account level
Also worth editing your post to remove your email address, it's publicly visible here and better kept out of community forums.
Hi @Sam Stoof
This sounds more like an account-side OAuth/login issue than a normal browser cache problem, especially since you already tested multiple browsers and private mode.
Since you already ruled out the common browser-side fixes, I would try:
1. confirm you are signing in with the exact Google account originally linked to that Loom account
2. test whether Google sign-in is blocked only for Loom or also for other Google-OAuth apps in that browser profile
3. if this is a Google Workspace-managed account, ask the Google admin whether Loom access is being restricted by OAuth/app policy
4. contact Loom support directly, because this looks like an OAuth/account-state problem rather than something you can fix from the client side
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ajay,
Thanks for the detailed response , I appreciate it. Unfortunately, I've already worked through all of these steps:
At this point it really does seem like something is broken at the account or OAuth token level on Loom's end. Hoping support can reset or relink the OAuth connection. I'll update this thread once I hear back.
Thanks again,
Sam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.