Supabase Troubleshooting

Resolve common Supabase authentication and connection issues

Supabase Status

Checking connection...

🚫 Error: OAuth Popup Closed

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: Configuration Missing

What it means: Supabase URL or Anon Key is missing from environment variables.

Common causes:

  • Missing .env.local file
  • Incorrect variable names (NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY)
  • Environment variables not added to Vercel project settings

Solutions:

  • Verify your .env.local file exists and contains the correct keys
  • Check Vercel project settings for environment variables
  • Restart the development server after changing environment variables

🌐 Network Connection Issues

If Supabase services are unreachable:

  • Check your internet connection
  • Verify your firewall isn't blocking Supabase domains
  • Try refreshing the page

🔧 Supabase Setup Checklist

Ensure these steps are completed:

  1. Supabase Project Setup:
    • Create project at Supabase Dashboard
    • Enable Google Auth Provider in Authentication settings
  2. URL Configuration:
    • Add your site URL to Redirect URLs in Supabase Auth settings
    • For local development: http://localhost:3000/auth/callback
    • For production: https://your-domain.com/auth/callback