{{ message }}
Replies: 2 comments
-
|
Hey @Tembogs! Can you please try using the direct connection string and check if it works for you? Use the non pooled connection string (without the pooler) for running migrate dev or db push commands. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
Question
C:\Users\mosho\PJC\backend\contact-support>npx prisma db push
[dotenv@17.2.4] injecting env (6) from .env -- tip: 🛠️ run anywhere with
dotenvx run -- yourcommandLoaded Prisma config from prisma.config.ts.
Prisma schema loaded from prisma\schema.prisma.
Datasource "db": PostgreSQL database "postgres", schema "public" at "aws-0-eu-west-1.pooler.supabase.com:5432"
Error: P1001: Can't reach database server at
aws-0-eu-west-1.pooler.supabase.com:5432Please make sure your database server is running at
aws-0-eu-west-1.pooler.supabase.com:5432. im trying to connect my prisma to my supabase database but keep hitting the error aboveHow to reproduce (optional)
Expected behavior (optional)
No response
Information about Prisma Schema, Client Queries and Environment (optional)
// Add your schema.prismagenerator client {
provider = "prisma-client-js"
}
datasource db {
provider = "postgresql"
}
OS: Windows
Database: PostgreSQL
Node.js version: v24.13.0
Run
prisma -vto see your Prisma version and paste itprisma : 7.6.0
@prisma/client : 7.6.0
Operating System : win32
Architecture : x64
Node.js : v24.13.0
TypeScript : 5.9.3
Query Compiler : enabled
PSL : @prisma/prisma-schema-wasm 7.6.0-1.75cbdc1eb7150937890ad5465d861175c6624711
Schema Engine : schema-engine-cli 75cbdc1eb7150937890ad5465d861175c6624711 (at node_modules@prisma\engines\schema-engine-windows.exe)
Default Engines Hash : 75cbdc1eb7150937890ad5465d861175c6624711
Studio : 0.27.3
Beta Was this translation helpful? Give feedback.
All reactions