Issue with data retrival Error: getaddrinfo ENOTFOUND

[kalithedev]

I'm encountering an issue where my APIs are unable to fetch data from the database. Specifically, the error I'm receiving is: Error: getaddrinfo ENOTFOUND db.database_url.supabase.co. This issue came up unexpectedly as there have been no recent changes to the codebase, and to the best of my knowledge, the database is not corrupted.

Here's a brief overview of the tech stack and relevant frameworks used in the project:

1. Next.js
2. React
3. NPM (Node Package Manager)
4. Database interaction tools: Prisma, GraphQL, Kysely

Could you provide guidance or suggestions on what might be causing this ENOTFOUND error and how to resolve it? Any insights into potential issues with the DNS resolution or other networking concerns related to db.database_url.supabase.co would be greatly appreciated.

[GaryAustin1]

https://github.com/orgs/supabase/discussions/17817
Most likely do to ipv4 to ipv6 transition. If the issue is with Prisma.

[kalithedev]

will try this

[kalithedev]

I tried switching to supavisor via this url postgres://postgres.lxrbpmzjqdsvvgvwvgep:[YOUR-PASSWORD]@aws-0-us-west-1.pooler.supabase.com:6543/postgres but our app could still not connect to the database

[Megahedron69]

Have you found a solution?

[InsightfulFuture]

I am having the same issue, but it also says it can't connect in the supabase dashboard & I am using the supabase client library. Any updates?

[Megahedron69]

I just change my dns whenever I work on the project (to cloudfare 1.1.1.1) and connection gets established but I have also not found any permanent solution Regards

…

On Mon, 1 Apr, 2024, 7:24 pm InsightfulFuture, ***@***.***> wrote: I am having the same issue, but it also says it can't connect in the supabase dashboard & I am using the supabase client library. Any updates? — Reply to this email directly, view it on GitHub <#20934 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATUGMD5Y2M4IYOXGGQSZGFTY3FRJJAVCNFSM6AAAAABCVE4HIGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSNZTGEZDO> . You are receiving this because you commented.Message ID: ***@***.***>

[joshberc]

Instead of using a direct connection string, use the Transaction or Session pooler connection string, resolved this issue for me. Using Drizzle to connect to a postgres DB on Supabase via drizzle.

[shaffatshah]

It actually says in my Supabase db setttings area that Pool mode is permanently set to Transaction on port 6543
You can use Session mode by connecting to the pooler on port 5432 instead and chosing 'Transaction' worked for me