Free tool · runs in your browser
Supabase error lookup: paste it, get the fix
Paste the error your app shows, from Supabase, Lovable, Bolt or the browser console. We match it against our 88 fix guides and show the one that explains it. Your error never leaves your browser.
Or browse every error we have a guide for, by where it comes from.
Supabase database
- Supabase "Could not find the table in the schema cache" (PGRST205)
404 · {"code":"PGRST205","details":null,"hint":null,"message":"Could not find the table 'public.todos' in the schema cache"} - Supabase "relation … does not exist" (42P01)
{"code":"42P01","details":null,"hint":null,"message":"relation \"public.orders\" does not exist"} - Supabase "canceling statement due to statement timeout" (57014)
{"code":"57014","details":null,"hint":null,"message":"canceling statement due to statement timeout"} - Supabase "Could not find the column in the schema cache" (PGRST204)
400 · {"code":"PGRST204","details":null,"hint":null,"message":"Could not find the 'userId' column of 'todos' in the schema cache"} - Supabase "Could not find the function in the schema cache" (PGRST202)
404 · {"code":"PGRST202","details":"Searched for the function public.get_stats with parameter userId or with a single unnamed json/jsonb parameter, but no matches were found in the schema cache.","hint":"Perhaps you meant to call the function public.get_stats(user_id)","message":"Could not find the function public.get_stats(userId) in the schema cache"} - Supabase "Could not embed because more than one relationship was found" (PGRST201)
Could not embed because more than one relationship was found for 'messages' and 'profiles' - Supabase "Could not find a relationship" error (PGRST200)
{"code":"PGRST200","details":"Searched for a foreign key relationship between 'orders' and 'profiles' in the schema 'public', but no matches were found.","hint":null,"message":"Could not find a relationship between 'orders' and 'profiles' in the schema cache"} - Supabase: column reference "id" is ambiguous (42702)
{"code":"42702","details":"It could refer to either a PL/pgSQL variable or a table column.","hint":null,"message":"column reference \"id\" is ambiguous"} - Supabase "operator does not exist: uuid = text" (42883)
ERROR: operator does not exist: uuid = text. HINT: No operator matches the given name and argument types. You might need to add explicit type casts. - Supabase "structure of query does not match function result type" (42804)
{"code":"42804","details":"Returned type bigint does not match expected type integer in column 2.","hint":null,"message":"structure of query does not match function result type"} - Supabase "Invalid path specified in request URL" (PGRST125)
404 · {"code":"PGRST125","details":null,"hint":null,"message":"Invalid path specified in request URL"} - Supabase 406 and PGRST116: "Cannot coerce the result to a single JSON object"
406 (Not Acceptable) · PGRST116 · Cannot coerce the result to a single JSON object · JSON object requested, multiple (or no) rows returned - Supabase "requested path is invalid": what it means and the fix
{"error":"requested path is invalid"} - Supabase "permission denied for table" (42501) since October 30: the safe fix
permission denied for table profiles · code 42501 · permission denied for sequence - Supabase RLS: "new row violates row-level security policy"
new row violates row-level security policy for table "profiles" - Supabase Storage upload fails: "new row violates row-level security policy"
new row violates row-level security policy · StorageApiError · upload to bucket refused - Supabase Storage "Bucket not found"
{"statusCode":"404","error":"Bucket not found","message":"Bucket not found","code":"NoSuchBucket"} - Supabase Storage "Object not found"
{"statusCode":"404","error":"not_found","message":"Object not found","code":"NoSuchKey"} - Supabase Storage "The resource already exists"
{"statusCode":"409","error":"Duplicate","message":"The resource already exists","code":"KeyAlreadyExists"} - Supabase Storage "The object exceeded the maximum allowed size"
{"statusCode":"413","error":"Payload too large","message":"The object exceeded the maximum allowed size","code":"EntityTooLarge"} - Supabase Storage "mime type … is not supported"
{"statusCode":"415","error":"invalid_mime_type","message":"mime type text/plain;charset=UTF-8 is not supported","code":"InvalidMimeType"} - Infinite recursion detected in policy for relation (Supabase): find the policy and break the loop
infinite recursion detected in policy for relation "..." · 42P17 · 500 - Supabase invalid input syntax for type uuid: "undefined" (22P02)
{"code":"22P02","details":null,"hint":null,"message":"invalid input syntax for type uuid: \"undefined\""} - Supabase "duplicate key value violates unique constraint" (23505)
{"code":"23505","details":"Key (id)=(1) already exists.","hint":null,"message":"duplicate key value violates unique constraint \"items_pkey\""} - Supabase "null value in column … violates not-null constraint" (23502)
{"code":"23502","details":null,"hint":null,"message":"null value in column \"user_id\" of relation \"notes\" violates not-null constraint"} - Supabase "new row for relation … violates check constraint" (23514)
{"code":"23514","details":null,"hint":null,"message":"new row for relation \"orders\" violates check constraint \"orders_status_check\""} - Supabase "value too long for type character varying" (22001)
{"code":"22001","details":null,"hint":null,"message":"value too long for type character varying(255)"} - Supabase "violates foreign key constraint" (23503)
{"code":"23503","details":"Key is not present in table \"posts\".","hint":null,"message":"insert or update on table \"comments\" violates foreign key constraint \"comments_post_id_fkey\""} - Security checklist for AI-built apps before you launch
RLS Disabled in Public · Table public.profiles is public, but RLS has not been enabled. - Supabase Realtime postgres_changes not working: SUBSCRIBED but no events (the real causes, tested)
SUBSCRIBED but no events · Unable to subscribe to changes with given parameters · Error parsing `filter` params · cannot add `postgres_changes` callbacks after `subscribe()`
Supabase Auth and logins
- Database error saving new user (Supabase): find the real error and fix sign-up
Database error saving new user · AuthApiError 500 · unexpected_failure - Supabase "Database error granting user" (500 at sign-in): find the trigger and fix it
Database error granting user · AuthRetryableFetchError 500 · unexpected_failure - Supabase "Database error querying schema" (500 at sign-in): find the broken rows and fix them
Database error querying schema · AuthRetryableFetchError 500 · unexpected_failure · converting NULL to string is unsupported - Supabase "Invalid login credentials" error
AuthApiError: Invalid login credentials · invalid_credentials · 400 - Supabase "Email not confirmed" error
AuthApiError: Email not confirmed · email_not_confirmed · Email address not authorized · email rate limit exceeded - Supabase "email rate limit exceeded" error
AuthApiError: email rate limit exceeded · over_email_send_rate_limit · 429 - Supabase "Request rate limit reached" (429)
AuthApiError: Request rate limit reached · over_request_rate_limit · 429 - Supabase: "Error sending confirmation email"
Error sending confirmation email · Email address not authorized - Supabase "User already registered" error
AuthApiError: User already registered · user_already_exists · 422 - Supabase "Signups not allowed for this instance"
AuthApiError: Signups not allowed for this instance · signup_disabled · 422 - Supabase "Anonymous sign-ins are disabled"
AuthApiError: Anonymous sign-ins are disabled · anonymous_provider_disabled · 422 - Supabase "Error sending recovery email"
AuthRetryableFetchError: Error sending recovery email · Error sending magic link email · 500 - Supabase "Error running hook URI" (Custom Access Token hook)
AuthRetryableFetchError: Error running hook URI: pg-functions://postgres/public/custom_access_token_hook · 500 - Supabase "User not allowed" (AuthApiError 403 not_admin)
AuthApiError: User not allowed · 403 · not_admin - Supabase "missing email or phone"
AuthApiError: missing email or phone · validation_failed · 400 - Supabase "captcha protection: request disallowed"
AuthApiError: captcha protection: request disallowed (no captcha_token found) · captcha_failed · 400 - Supabase "Database error deleting user"
{"code":500,"error_code":"unexpected_failure","msg":"Database error deleting user"} - Supabase "New password should be different from the old password"
AuthApiError: New password should be different from the old password. · same_password · 422 - Supabase "Password should be at least 6 characters"
AuthWeakPasswordError: Password should be at least 6 characters. · weak_password · 422 - Supabase "Unable to validate email address: invalid format"
AuthApiError: Unable to validate email address: invalid format · validation_failed · 400 - Supabase "Email address is invalid"
AuthApiError: Email address "test@example.com" is invalid · email_address_invalid · 400 - Supabase "Auth session missing!" error
AuthSessionMissingError: Auth session missing! · session_not_found · PKCE code verifier not found in storage - Supabase "invalid flow state, no valid flow state found"
AuthApiError: invalid flow state, no valid flow state found · flow_state_not_found · invalid flow state, flow state has expired - Supabase "Invalid Refresh Token: Refresh Token Not Found"
Invalid Refresh Token: Refresh Token Not Found · refresh_token_not_found · Invalid Refresh Token: Already Used · AuthApiError - Supabase "JWT expired" (PGRST303)
{"code":"PGRST303","details":null,"hint":null,"message":"JWT expired"} - Supabase "Email link is invalid or has expired" (otp_expired)
Email link is invalid or has expired · otp_expired · error=access_denied - Supabase "Token has expired or is invalid" (email OTP)
{"code":"otp_expired","message":"Token has expired or is invalid"} - Supabase auth "Failed to fetch": why login fails and how to fix it
AuthRetryableFetchError: Failed to fetch · TypeError: Failed to fetch · Load failed - Chrome "Permission was denied for this request to access the loopback address space"
Access to fetch at 'http://127.0.0.1:54321/…' has been blocked by CORS policy: Permission was denied for this request to access the `loopback` address space. - Supabase login redirects to localhost after deploy
http://localhost:3000/#access_token=… · This site can't be reached - Google login "Error 400: redirect_uri_mismatch": the fix for Supabase and Lovable apps
Access blocked: This app's request is invalid. Error 400: redirect_uri_mismatch - Supabase "Unsupported provider: provider is not enabled"
{"code":400,"error_code":"validation_failed","msg":"Unsupported provider: provider is not enabled"} - Supabase "invalid claim: missing sub claim" (403 bad_jwt)
AuthApiError: invalid claim: missing sub claim · 403 · bad_jwt
Edge Functions, Stripe and email
- Edge Function returned a non-2xx status code: read the real error and fix it
Edge Function returned a non-2xx status code · FunctionsHttpError · Failed to send a request to the Edge Function - Supabase Edge Function "blocked by CORS policy": every message, fixed
Access to fetch at '…/functions/v1/…' has been blocked by CORS policy · Response to preflight request doesn't pass access control check · FunctionsFetchError - Supabase Edge Function "Missing authorization header" (401)
401 · {"code":"unauthorized_no_auth_header","message":"Missing authorization header"} - Stripe webhook secret: where to find it, and fixing 400/401 errors
No signatures found matching the expected signature for payload - Resend "You can only send testing emails to your own email address": the fix
You can only send testing emails to your own email address (you@example.com). To send emails to other recipients, please verify a domain at resend.com/domains, and change the `from` address to an email using this domain. - Edge Function 546 "not having enough compute resources" (WORKER_RESOURCE_LIMIT)
{"code":"WORKER_RESOURCE_LIMIT","message":"Function failed due to not having enough compute resources (please check logs)"} - Edge Function 503 BOOT_ERROR "Function failed to start (please check logs)"
{"code":"BOOT_ERROR","message":"Function failed to start (please check logs)"} - Edge Function 404 "Requested function was not found" (NOT_FOUND)
{"code":"NOT_FOUND","message":"Requested function was not found"}
Lovable
- Lovable app: blank page or Vercel 404 after deploy
404: NOT_FOUND · supabaseUrl is required. - Lovable code won't run locally after export or GitHub sync
npm run dev fails · blank page on localhost · supabaseUrl is required · listen EAFNOSUPPORT :::8080 · bunx: not found - Lovable build unsuccessful: find the real error and fix it without burning credits
Fix build errors · failed to resolve import · is not exported by · Publishing failed - Lovable publish not working: changes not showing, Publishing failed, or no Publish button
Publishing failed · Fix build errors · latest changes not on the live site - Lovable "Try to fix" button: what it does, when it's free, and what to do when it keeps failing
Try to fix · Try to fix all · Fix build errors · Publishing failed - Lovable preview not working (not loading, blank, or not updating)
preview not loading · white preview · not updating · « Preview has not been built yet » - Lovable published site not working (but the preview works)
works in the preview · broken on the published site - Lovable custom domain not working: DNS, SSL and Cloudflare fixes
Looking for your DNS records · Issuing certificate · Error 1034: Edge IP Restricted · Error 1001: DNS resolution error - Lovable published site "Not secure" (browser warning or security scan)
Not secure · Your connection is not private · ERR_TOO_MANY_REDIRECTS · Dangerous site · 2 critical security issues found - Lovable GitHub connection not working: sync, missing commits and reconnect fixes
GitHub is N commits ahead of Lovable · Lovable and GitHub have diverged · This repository is no longer accessible - Lovable remix blocked: why you can't remix a project and how to fix it
can't remix a project · Remix missing · the link says the project is private · Projects with payments cannot be remixed - Lovable Website Takedown Notice: why your site was taken down and how to appeal
Website Takedown Notice · This website has been taken down · Website Suspended · temporarily suspended for violating our community guidelines - Lovable site not showing up on Google
site: search shows nothing · URL is not on Google · Discovered – currently not indexed · Blocked by robots.txt
Bolt, Replit and others
- Bolt error 500 (Internal Server Error): find which part of your app failed and fix it
500 (Internal Server Error) · Edge Function returned a non-2xx status code · Database error saving new user · infinite recursion detected in policy - Bolt preview not working: blank screen, stuck loading, or WebContainer error
Your preview will appear here · blank, white or gray preview · Out of memory · Building a hosted preview of your app - Replit app not working: blank Preview, failed publish, or broken live app
Application failed to respond · 502 Bad Gateway · The endpoint has been disabled · publishing failed - Upload your iOS app to the App Store without a Mac (from Windows)
Transporter for Windows not working · no Mac to upload the .ipa · how to upload an ipa without a Mac