© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•3y ago•
17 replies
AstroBear

Authentication error when using connection pooling

I'm trying to use connection pooling with NodeJS, using Prisma.

However, while the default connection works fine, when I try to use pooling I get the following error:
Error in connector: Error querying the database: FATAL: Authentication error
Error in connector: Error querying the database: FATAL: Authentication error


Here are my connection strings:
DATABASE_URI="postgres://postgres:[PASSWORD]@db.[ID].supabase.co:5432/postgres"
POOL_DATABASE_URI="postgres://postgres.[ID]:[PASSWORD]@aws-0-eu-central-1.pooler.supabase.com:6543/postgres"
DATABASE_URI="postgres://postgres:[PASSWORD]@db.[ID].supabase.co:5432/postgres"
POOL_DATABASE_URI="postgres://postgres.[ID]:[PASSWORD]@aws-0-eu-central-1.pooler.supabase.com:6543/postgres"


Am I missing something?

There is this log on logs/pooler:
Authentication auth_secrets error: "Authentication query failed: %DBConnection.ConnectionError{message: \"connection not available and request was dropped from queue after 2000ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:\\n\\n  1. Ensuring your database is available and that you can connect to it\\n  2. Tracking down slow queries and making sure they are running fast enough\\n  3. Increasing the pool_size (although this increases resource consumption)\\n  4. Allowing requests to wait longer by increasing :queue_target and :queue_interval\\n\\nSee DBConnection.start_link/2 for more information\\n\", severity: :error, reason: :queue_timeout}"
Authentication auth_secrets error: "Authentication query failed: %DBConnection.ConnectionError{message: \"connection not available and request was dropped from queue after 2000ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:\\n\\n  1. Ensuring your database is available and that you can connect to it\\n  2. Tracking down slow queries and making sure they are running fast enough\\n  3. Increasing the pool_size (although this increases resource consumption)\\n  4. Allowing requests to wait longer by increasing :queue_target and :queue_interval\\n\\nSee DBConnection.start_link/2 for more information\\n\", severity: :error, reason: :queue_timeout}"
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

Connection Pooling & Prisma
SupabaseSSupabase / help-and-questions
4y ago
Connection Pooling with PgBouncer
SupabaseSSupabase / help-and-questions
4y ago
DB Access denied when connecting via Connection Pooling
SupabaseSSupabase / help-and-questions
3y ago
Connection pooling with different user
SupabaseSSupabase / help-and-questions
3y ago