P
Prisma•3w ago
komo

Error creating a database connection

Hi, I get errors when trying to view studio of my new database cme7b43dz02es09m0d03dkuq3.
{"error":"Error in connector: Error creating a database connection. (Error in the underlying connector)","user_facing_error":{"is_panic":false,"message":"Can't reach database server at `database-01k27ccdyybvwkw4emed4ryn47.cdg1.db.prisma-data.net:5432`\n\nPlease make sure your database server is running at `database-01k27ccdyybvwkw4emed4ryn47.cdg1.db.prisma-data.net:5432`.","meta":{"database_host":"database-01k27ccdyybvwkw4emed4ryn47.cdg1.db.prisma-data.net","database_port":5432},"error_code":"P1001"}}
{"error":"Error in connector: Error creating a database connection. (Error in the underlying connector)","user_facing_error":{"is_panic":false,"message":"Can't reach database server at `database-01k27ccdyybvwkw4emed4ryn47.cdg1.db.prisma-data.net:5432`\n\nPlease make sure your database server is running at `database-01k27ccdyybvwkw4emed4ryn47.cdg1.db.prisma-data.net:5432`.","meta":{"database_host":"database-01k27ccdyybvwkw4emed4ryn47.cdg1.db.prisma-data.net","database_port":5432},"error_code":"P1001"}}
After some time it works again without any issue and then fails with the same error again. My production app cannot make any query.
10 Replies
Prisma AI Help
Prisma AI Help•3w ago
You're in no rush, so we'll let a dev step in. Enjoy your coffee, or drop into #ask-ai if you get antsy for a second opinion!
Nurul
Nurul•3w ago
Hey @komo I am getting this checked. Can you try restarting database instance from Settings page in Prisma Console and check if you still get the same error? Can you let me know if you are using prisma+postgres:// connection string or the direct connection string starting with postgres://?
komo
komoOP•3w ago
I used the direct connection string postgres:// I also had the errors on the hosted studio though I will try to restart Thanks what's the difference between the 2 connection strings?
Nurul
Nurul•3w ago
We saw some connection limits related error. We are increasing that limit for you. You can continue using direct connection string The Accelerate connection string allows you to do caching while the direct connection string does not
komo
komoOP•3w ago
got it, thanks a lot
komo
komoOP•3w ago
sorry @Nurul , still have the same issue. Maybe one of my requests is crashing the database 😅
No description
komo
komoOP•3w ago
here are my vercel logs
{"level":50,"time":"2025-08-12T16:14:45.094Z","err":{"type":"DatabaseError","message":"Startup/auth proxy error","stack":"error: Startup/auth proxy error\n at file:///var/task/build/server/nodejs_eyJydW50aW1lIjoibm9kZWpzIn0/index.js:46413:13\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async file:///var/task/build/server/nodejs_eyJydW50aW1lIjoibm9kZWpzIn0/index.js:50514:23\n at async readData (file:///var/task/build/server/nodejs_eyJydW50aW1lIjoibm9kZWpzIn0/index.js:50957:25)\n at async getSession (file:///var/task/build/server/nodejs_eyJydW50aW1lIjoibm9kZWpzIn0/index.js:5254:26)\n at async requireUser (file:///var/task/build/server/nodejs_eyJydW50aW1lIjoibm9kZWpzIn0/index.js:154517:19)\n at async action$1 (file:///var/task/build/server/nodejs_eyJydW50aW1lIjoibm9kZWpzIn0/index.js:162468:17)\n at async callRouteHandler (/var/task/node_modules/react-router/dist/development/index.js:10393:16)\n at async /var/task/node_modules/react-router/dist/development/index.js:4292:19\n at async callLoaderOrAction (/var/task/node_modules/react-router/dist/development/index.js:4344:16)","length":31,"name":"error"},"msg":"Startup/auth proxy error"}
{"level":50,"time":"2025-08-12T16:14:45.094Z","err":{"type":"DatabaseError","message":"Startup/auth proxy error","stack":"error: Startup/auth proxy error\n at file:///var/task/build/server/nodejs_eyJydW50aW1lIjoibm9kZWpzIn0/index.js:46413:13\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async file:///var/task/build/server/nodejs_eyJydW50aW1lIjoibm9kZWpzIn0/index.js:50514:23\n at async readData (file:///var/task/build/server/nodejs_eyJydW50aW1lIjoibm9kZWpzIn0/index.js:50957:25)\n at async getSession (file:///var/task/build/server/nodejs_eyJydW50aW1lIjoibm9kZWpzIn0/index.js:5254:26)\n at async requireUser (file:///var/task/build/server/nodejs_eyJydW50aW1lIjoibm9kZWpzIn0/index.js:154517:19)\n at async action$1 (file:///var/task/build/server/nodejs_eyJydW50aW1lIjoibm9kZWpzIn0/index.js:162468:17)\n at async callRouteHandler (/var/task/node_modules/react-router/dist/development/index.js:10393:16)\n at async /var/task/node_modules/react-router/dist/development/index.js:4292:19\n at async callLoaderOrAction (/var/task/node_modules/react-router/dist/development/index.js:4344:16)","length":31,"name":"error"},"msg":"Startup/auth proxy error"}
Do I need pooling or something?
Nurul
Nurul•3w ago
Sorry for the delay in getting back. Let me inform our team internally
komo
komoOP•2w ago
no worries, thanks for getting back to me any news on this?
Nurul
Nurul•7d ago
There doesn't seem to be any obvious issues that we can see. This issue seems specific to Prisma Studio, are you using enums in your prisma schema by any chance? Are all of your queries failing with this same error? There are ample connections available for your database instance.

Did you find this page helpful?