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.

Jaime Orts-Caroff Jaime Orts-Caroff I'm a Senior Android developer, open to work in various fields Costea Adrian Costea Adrian Embedded Engineer specilizing in perception systems. Latest project was a adas camera calibration system. Nam Tran Nam Tran 10 years as fullstack developer Anthony Akpan Anthony Akpan Developer with 8 years of experience building softwares fro startups 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. AUXLE AUXLE I am a Full Stack Developer experienced in building Websites, Web apps and Cross Platform Mobile Apps for Startups and Companies. Krishna Sai Kuncha Krishna Sai Kuncha Experienced Professional Full stack Developer with 8+ years of experience across react, python, js, ts, golang and react-native. Developed inhouse websearch tooling for AI before websearch was solved : ) Luca Liberati Luca Liberati I work on monoliths and microservices, backends and frontends, manage K8s clusters and love to design apps architecture zipking zipking I am a technologist and product builder dedicated to creating high-impact solutions at the intersection of AI and specialized markets. Currently, I am focused on PropScan (EstateGuard), an AI-driven SaaS platform tailored for the Japanese real estate industry, and exploring the potential of Archify. As an INFJ-T, I approach development with a "systems-thinking" mindset—balancing technical precision with a deep understanding of user needs. I particularly enjoy the challenge of architecting Vertical AI SaaS and optimizing Small Language Models (SLMs) to solve specific, real-world business problems. Whether I'm in a CTO-level leadership role or hands-on with the code, I thrive on building tools that turn complex data into actionable value. 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