OAuth2 Provider Not Configured - Missing Client ID
Your OAuth2 provider (Google, GitHub, Facebook) authentication fails immediately with cryptic errors. The login redirect works but authorization fails.
Common signs: blank page on OAuth callback, 'client_id not found' in browser console, or authentication loops indefinitely.
Error Messages You Might See
Common Causes
- Environment variable for OAuth client ID is undefined or mistyped
- Redirect URI registered with provider doesn't match application URI
- OAuth credentials copied incorrectly from provider dashboard
- Mixed up client ID and client secret values
- Development vs production configuration mismatch
How to Fix It
Verify environment variables are loaded: console.log(process.env.NEXT_PUBLIC_OAUTH_CLIENT_ID)
Check OAuth provider dashboard (Google Cloud Console, GitHub Settings) - ensure 'Authorized redirect URIs' includes your Bolt app URL.
Validate the redirect URI format matches exactly: https://your-app.bolt.new/api/auth/callback
Real developers can help you.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
Where do I find OAuth credentials?
Visit your OAuth provider's developer dashboard. For Google: console.cloud.google.com. For GitHub: github.com/settings/developers
What's the correct redirect URI format?
Use https://your-app-name.bolt.new/api/auth/callback for Bolt deployments
Can I test OAuth locally?
Yes, but use localhost:3000/api/auth/callback in your provider settings, then switch to production URI before deploying