Guide
Firebase Google sign-in not working: "This domain is not authorized to run this operation"
Updated
A new person taps Google sign-in on your app and gets an error, such as "This domain is not authorized to run this operation", or lands back on the login page. This applies to apps from AI builders that use Firebase Authentication.
Why it happens
Firebase checks that the Google provider is on and that the domain the sign-in redirects from is on its authorized list.
Possible causes
- The Google sign-in provider is not enabled in Firebase Authentication.
- The domain your app runs on is not in the authorized domains list.
- You use a custom domain, but the app still points at the project's default sign-in domain, or the redirect page on your domain is not allowed in the Google setup.
- The client ID and secret in Firebase do not match the web client in the Google Cloud credentials ("invalid OAuth client ID").
- The browser API key was deleted or restricted so that it no longer allows Firebase Authentication.
You can't see it yourself
You're signed in, your customers aren't. You tested on an address that is already authorized, such as localhost or the default Firebase domain.
Related: "Sign in with Google" fails for new people on my live app · New users sign up, then land back on the login page or see an error · Sign-up or login broken after publishing: users bounce back to login or land on localhost
VibeFix is independent. Lovable, Bolt, Replit, Base44, v0, Supabase, Firebase, Stripe and Vercel are trademarks of their owners.
Want it fixed?
Our AI agent finds the cause, fixes it in your code and re-checks your live app. $79 for one bug, paid up front. If we can't complete your re-check, you get your money back.
It starts with a free check that confirms the problem on your live app, no account needed.