Base44 auth

Google or Social Login Not Working in Base44 App

You have enabled Google login (or another social OAuth provider) in your Base44 app, but clicking the social login button results in an error. Users may see a Google error page, a "redirect_uri_mismatch" message, or get redirected back to the login page without being authenticated.

This issue is particularly frustrating because social login often works perfectly in the Base44 editor preview but breaks in the published version of the app. The OAuth flow requires precise URL matching that can easily go wrong between environments.

Error Messages You Might See

Error 400: redirect_uri_mismatch Access blocked: This app's request is invalid Error: invalid_client
Error 400: redirect_uri_mismatchAccess blocked: This app's request is invalidError: invalid_client

Common Causes

  1. The OAuth redirect URI configured in your Google/social provider console doesn't match the published app's URL
  2. Client ID or client secret was copied incorrectly or contains extra whitespace
  3. The OAuth consent screen has not been published or is still in testing mode with limited test users
  4. The app's published domain changed (e.g., custom domain added) but the OAuth provider wasn't updated

How to Fix It

Double-check the redirect URI in your OAuth provider's console (e.g., Google Cloud Console). It must exactly match the URL Base44 uses for the callback, including the protocol (https) and any path segments.

If using Google, make sure your OAuth consent screen is configured for production use, not just testing. In testing mode, only explicitly listed test users can log in.

OAuth configuration involves multiple systems and precise URL matching. If you've verified the basics and the issue persists, a developer experienced with OAuth flows can quickly identify the mismatch.

Real developers can help you.

Jen Jacobsen Jen Jacobsen I’m a Full-Stack Developer with over 10 years of experience building modern web and mobile applications. I enjoy working across the full product lifecycle — turning ideas into real, well-built products that are intuitive for users and scalable for businesses. I particularly enjoy building mobile apps, modern web platforms, and solving complex technical problems in a way that keeps systems clean, reliable, and easy to maintain. Taufan Taufan I’m a product-focused engineer and tech leader who builds scalable systems and turns ideas into production-ready platforms. Over the past years, I’ve worked across startups and fast-moving teams, leading backend architecture, improving system reliability, and shipping products used by thousands of users. My strength is not just writing code — but connecting product vision, technical execution, and business impact. prajwalfullstack prajwalfullstack Hi Im a full stack developer, a vibe coded MVP to Market ready product, I'm here to help Antriksh Narang Antriksh Narang 5 years+ Experienced Dev (Specially in Web Development), can help in python, javascript, react, next.js and full stack web dev technologies. Matt Butler Matt Butler Software Engineer @ AWS Rudra Bhikadiya Rudra Bhikadiya I build and fix web apps across Next.js, Node.js, and DBs. Comfortable jumping into messy code, broken APIs, and mysterious bugs. If your project works in theory but not in reality, I help close that gap. Tejas Chokhawala Tejas Chokhawala Full-stack engineer with 5 years experience building production web apps using React, Next.js and TypeScript. Focused on performance, clean architecture and shipping fast. Experienced with Supabase/Postgres backends, Stripe billing, and building AI-assisted developer tools. Costea Adrian Costea Adrian Embedded Engineer specilizing in perception systems. Latest project was a adas camera calibration system. Pratik Pratik SWE with 15+ years of experience building and maintaining web apps and extensive BE infrastructure Bastien Labelle Bastien Labelle Full stack dev w/ 20+ years of experience

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help

Frequently Asked Questions

Why does Google login fail in my published Base44 app but work in preview?

The published app uses a different URL than the editor preview. You need to add your published app's URL as an authorized redirect URI in the Google Cloud Console.

How do I fix redirect_uri_mismatch in Base44?

Go to your OAuth provider's console and add the exact callback URL your published Base44 app uses. The URL must match exactly, including https and the full path.

Related Base44 Issues

Can't fix it yourself?
Real developers can help.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help