Fauna Not Working: Connection Refused or Request Failed

How to fix it

Try these in order — the most common fix is first.

1. 1. Stop the errors in production

   Copy steps
   1. Search your code and env vars for Fauna secrets and endpoints
   2. Add a clear failure message or feature flag around Fauna calls
   3. Redirect traffic to your new database as soon as it is ready
   Did this fix it? Yes No

2. 2. Do not debug the Fauna side

   Copy steps
   1. Rotating keys or upgrading the driver will not help
   2. Remove the Fauna SDK once migration is finished
   Did this fix it? Yes No

Symptoms

Driver calls fail with connection errors, timeouts or authentication failures; the dashboard is unreachable.

Why it happens

• Service shut down May 30, 2025
• Secrets in your app still point to Fauna endpoints
• Serverless deploys keep failing at cold start

This guide also covers

• fauna not working
• faunadb connection refused
• fauna error
• fauna api down

The same problem in other apps

All not loading, error messages & connection guides →

• Supabase Max Client Connections Reached (Supabase)
• Neon Connection Timeout After Scale to Zero (Cold Start) (Neon)
• MongoDB Atlas Connection Timed Out (IP Not Whitelisted) (MongoDB Atlas)
• PlanetScale Prisma Connection Errors (PlanetScale)

Other Fauna errors

• Is Fauna Shutting Down? What Happened and What to Do
• How to Export Your Data from Fauna (Before and After Shutdown)
• How to Migrate from Fauna to Postgres
• How to Migrate from Fauna to MongoDB
• Is Fauna Open Source? Can You Self-Host It?
• Fauna Billing After Shutdown: Charges, Refunds and Cancel
• Converting FQL Queries to SQL After Fauna
• Fauna GraphQL and REST API Not Responding After Shutdown