Firebase Troubleshooting
Resolve common Firebase authentication and connection issues
Firebase Status
Checking connection...
🚫 Error: auth/popup-closed-by-user
What it means: The Google sign-in popup was closed before completing authentication.
Solutions:
- Make sure to complete the sign-in process in the popup window
- Don't close the popup before selecting your Google account
- Check if popup blockers are preventing the window from opening
- Try disabling browser extensions that might interfere
⚠️ Error: 400 Status Response
What it means: Bad request to Firebase servers, usually due to configuration issues.
Common causes:
- Invalid Firebase project configuration
- Incorrect API keys or project settings
- Domain not authorized in Firebase console
- Authentication methods not enabled
Solutions:
- Verify your Firebase project settings in the Firebase Console
- Add your domain to authorized domains: Firebase Console → Authentication → Settings → Authorized domains
- Enable email/password and Google authentication methods
- Check that your API key is valid and hasn't been restricted
🌐 Network Connection Issues
If Firebase services are unreachable:
- Check your internet connection
- Verify your firewall isn't blocking Firebase domains
- Try refreshing the page
- Check if your network blocks googleapis.com or firebase.com
🔧 Firebase Setup Checklist
Ensure these steps are completed:
- Firebase Project Setup:
- Create project at Firebase Console
- Enable Authentication service
- Enable Email/Password and Google sign-in methods
- Domain Authorization:
- Add localhost:3000 to authorized domains (for development)
- Add your production domain when deploying
- Configuration:
- Copy your web app configuration from Firebase Console
- Update src/lib/firebase.ts with your config
- Ensure all required fields are filled correctly
- Test Users:
- Create test users in Firebase Console
- Or allow user registration in your Authentication settings
🌐 Browser Compatibility
For best results:
- Use a modern browser (Chrome, Firefox, Safari, Edge)
- Enable cookies and JavaScript
- Disable strict tracking protection for this site
- Allow popups from this domain
- Clear browser cache if experiencing issues