Why has Supabase stopped connecting?
Last checked 31 Aug 2026
Short answer
Usually an expired/rotated key, a paused free-tier project, an RLS policy change, or a genuine outage. Check the connection status and error message in Lovable before assuming your code broke.
Diagnostic sequence
- Check the exact error — "failed to connect", a timeout, or an auth/permission error each point to different causes.
- Ask Lovable to confirm the current connection status to your Supabase project (Lovable Cloud or your own connected Supabase project).
- If you're on your own Supabase project (not Lovable Cloud): check whether it's on the free tier and has been paused due to inactivity — Supabase pauses free projects after a period without activity, and this is fixed from Supabase's own dashboard, not Lovable.
- Check whether any API keys were recently rotated at the Supabase project level without updating them in Lovable.
- Check Logs for the specific error type — a connection-level failure looks different from an RLS/permission denial.
Lovable Cloud vs. your own Supabase project
| Setup | Where to check |
|---|---|
| Lovable Cloud | Ask Lovable to check the connection and configuration — there's no separate dashboard to log into. |
| Your own Supabase project | Check your Supabase project's status directly (e.g. whether it's paused) as well as asking Lovable to verify the connection settings on its side. |
What usually goes wrong
- A self-managed Supabase project on the free tier gets auto-paused after inactivity, which looks identical to "Supabase stopped connecting" from inside Lovable.
- A key was regenerated in Supabase (intentionally or via a security rotation) but the new key was never given to Lovable.
- A recent RLS policy change unintentionally blocks the specific query that's now failing, which presents as a connection problem but is actually a permissions one.
Fixing it
The app can't connect to Supabase. Error: [paste exact message]. Check the current connection configuration and confirm whether the keys are still valid.
If you're on your own Supabase project and it turns out to be paused, resume it from Supabase directly, then ask Lovable to reconnect. For anything unclear, PromptSites.com can check both sides of the connection quickly.
Sources
Was this answer helpful?
Related questions
- AnswerWhy is Lovable chat stuck loading?Chat usually gets stuck loading due to a network blip, a very large/complex request, or a backend timeout. Refresh first, then check the console before resending the same prompt.
- AnswerHow do I fix a Lovable build error?Read the exact error message and file it points to, paste it back to Lovable, and let it fix that specific error rather than describing the symptom vaguely.
- AnswerWhy is my custom domain offline?Custom domains usually go offline because of a missing or changed DNS record, a certificate that hasn't issued yet, or the registrar's records pointing somewhere else — recheck the domain settings and your DNS provider.
- AnswerWhy am I getting "Failed to Fetch"?"Failed to fetch" means the browser couldn't complete a network request at all — usually CORS, a down endpoint, a missing/invalid API key, or no internet connection, rather than a code logic error.
