Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to log in to Loom – Google OAuth authentication failure

Sam Stoof
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 11, 2026

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

2 answers

1 vote
Arkadiusz Wroblewski
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 11, 2026

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.

0 votes
Ajay _view26_
Community Champion
April 11, 2026

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

 

Sam Stoof
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 12, 2026

Hi Ajay,

Thanks for the detailed response , I appreciate it. Unfortunately, I've already worked through all of these steps:

  1. Correct Google account — Yes, I'm signing in with the exact account originally linked to my Loom account.
  2. Google OAuth on other apps — Google sign-in works without issue on all other OAuth-connected apps in the same browser profile, so it appears to be Loom-specific.
  3. Google Workspace policy — This is a personal Google account, not a Workspace-managed one, so admin restrictions aren't a factor here.
  4. Loom support — Since I'm fully locked out and can't access the in-app form, I've followed Arkadiusz's suggestion and reached out via support.atlassian.com directly.

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

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events