← All errors

Supabase errors and fixes

Supabase auth, row-level security (RLS), schema and Edge Function errors that show up in AI-built apps.

10 Supabase errors below. Each page shows the exact error text, what it means, likely causes and a step-by-step fix.

• new row violates row-level security policy for table
  Row Level Security is enabled on the table and no policy allows the current user to insert (or update) this row.
• Supabase select returns an empty array (no error)
  With RLS enabled and no SELECT policy matching the user, Postgres silently filters out all rows.
• Invalid JWT / JWT expired
  The access token sent to Supabase is expired or was signed with a different project's secret..
• supabaseUrl is required
  createClient() was called with an undefined URL, usually because an environment variable is missing..
• relation "public.x" does not exist
  Postgres can't find the table or view.
• Could not find the column in the schema cache
  The PostgREST API layer doesn't know about this column, either because it doesn't exist or the API's schema cache is stale.
• Email rate limit exceeded
  Supabase's built-in email service has a low hourly sending limit intended for testing, and your project hit it..
• TypeError: Failed to fetch (Supabase Edge Function / CORS)
  The browser blocked the response because the Edge Function did not return CORS headers, often on the OPTIONS preflight request..
• AuthApiError: Invalid login credentials
  signInWithPassword was rejected: no user with that email/password combination could be authenticated..
• AuthApiError: Email not confirmed
  Email confirmation is enabled and this user hasn't clicked the confirmation link yet..

Related error categories

• Serverless & Edge Function errors: 4 pages
• Supabase auth errors: 5 pages
• Supabase database & RLS errors: 4 pages

Not sure which one you have? Take the quiz →

Other platforms

Next.js · Vercel · Stripe · Cursor · Lovable · Bolt · Replit