Bolt.new Supabase Connection Not Working

How to fix it

// try these in order, the most common fix is first

1. FIX 1Check status and project keys

   Copy steps
   1. 01Open status.bolt.new
   2. 02Confirm the Supabase URL and anon key belong to the project you intend
   Did this fix it? Yes No

2. FIX 2Reset RLS

   Copy steps
   1. 01Ask Bolt to remove all RLS rules from the table
   2. 02Ask it to add the correct rule, describing the behavior
   3. 03Confirm RLS is enabled in Supabase
   Did this fix it? Yes No

3. FIX 3Use secrets for server calls

   Copy steps
   1. 01Click the database icon > Secrets
   2. 02Add the exact name the code expects and save
   Did this fix it? Yes No

4. FIX 4Under load

   1. 01Use Supabase's pooled connection string
   Did this fix it? Yes No

Symptoms

Data missing, authorization errors, credentials pointing at the wrong database, or too many connections.

Why it happens

• C-01Credentials reverted or exported project points elsewhere
• C-02RLS misconfigured or disabled
• C-03Environment variables not set on the host
• C-04Connection per request under load

// this guide also covers

• bolt.new supabase not connecting
• bolt.new supabase error
• bolt.new rls not working

The same problem in other apps

All not loading, error messages & connection guides →

• Lovable Stuck in an Error Loop (Lovable)
• Replit Workspace Not Loading (Replit)
• Cursor High Load Error (ERROR_RESOURCE_EXHAUSTED) (Cursor)
• Bubble Workload Units Running Out Too Fast (Bubble)
• GitHub Copilot Proxy and Certificate Errors (GitHub Copilot)

Other Bolt.new errors

• Bolt.new Tokens Burning Fast
• Bolt.new Error Loop
• Bolt.new Ran Out of Tokens
• Bolt.new Project Too Large to Deploy
• Bolt.new Netlify Publish Failed
• Bolt.new Site Shows 404 After Publishing
• Bolt.new GitHub Sync Not Working
• Bolt.new Missing Secrets and CORS Errors