Find out why Supabase is rejecting my requests | Vovy
Vovy opens Supabase Logs for your API, database, auth and edge functions, finds the failing requests, and explains each error with the fix.
Check my Supabase logs and tell me why requests are failing
How it works
- Open Logs and Analytics: Vovy opens your Supabase project and goes to Logs, where each service, API gateway, Postgres, Auth, Storage and Edge Functions, has its own stream.
- Filter the API gateway to failures: It filters API requests to 4xx and 5xx status codes so you see only the calls that failed, with the table and method for each.
- Check Postgres for the real reason: A 401 or empty result often traces back to Postgres. Vovy looks for messages like "permission denied for table" or "new row violates row-level security policy".
- Match it to your browser request: It reproduces the failing action in Chrome with the Network tab open so the error in the log lines up with the button you clicked.
- Explain the cause and fix: You get a card per error: what it means, whether it is a policy, key or schema problem, and the exact change to make.
What you provide
- Access to your Supabase project
- The action in your app that fails
What you get
- The failing requests, filtered
- Root cause for each error
- The policy, key or schema fix
FAQ
Why does my query return an empty list and no error?
That is usually Row Level Security working as designed: no policy allows that user to read those rows, so Postgres returns nothing instead of an error.
How far back do logs go?
The free plan keeps about a day of logs; paid plans keep longer. Reproduce the problem right before checking.
Is it safe for Vovy to read these logs?
Yes. Reading logs changes nothing in your project, and Vovy asks before running any SQL that edits data or policies.
Related tasks
All tasksLoading...