a month ago
I'm having several connection issues with my Neon database and the database connected to the same infrastructure as yours.
6 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
MistcPay project:
Can't reach database server at ep-silent-truth-apcgmiyb-pooler.c-7.us-east-1.aws.neon.tech:5432
Please make sure your database server is running at ep-silent-truth-apcgmiyb-pooler.c-7.us-east-1.aws.neon.tech:5432.
at ei.handleRequestError (/app/node_modules/.pnpm/@prisma+client@6.18.0_prisma@6.18.0_typescript@5.9.3__typescript@5.9.3/node_modules/@prisma/client/runtime/library.js:121:7568)
at ei.handleAndLogRequestError (/app/node_modules/.pnpm/@prisma+client@6.18.0_prisma@6.18.0_typescript@5.9.3__typescript@5.9.3/node_modules/@prisma/client/runtime/library.js:121:6593)
at ei.request (/app/node_modules/.pnpm/@prisma+client@6.18.0_prisma@6.18.0_typescript@5.9.3__typescript@5.9.3/node_modules/@prisma/client/runtime/library.js:121:6300)
at async a (/app/node_modules/.pnpm/@prisma+client@6.18.0_prisma@6.18.0_typescript@5.9.3__typescript@5.9.3/node_modules/@prisma/client/runtime/library.js:130:9551)ZorinPay Project:
[Nest] 31 - 07/18/2026, 4:47:22 AM ERROR [WithdrawalProcessor] [process-withdrawal] Erro no worker (BullMQ) | read ECONNRESET +15870ms
Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:216:20)Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:216:20) {errno: -104,
code: 'ECONNRESET',
syscall: 'read'
}
Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:216:20) {errno: -104,
code: 'ECONNRESET',
syscall: 'read'
}
a month ago
Try adding ?pgbouncer=true to the URL (and set SSL to require if it isn't).
a month ago
I have one project where I'm using your database and another where I use Neon's. The one using your database gives me this error:
[Nest] 31 - 07/18/2026, 3:45:43 PM ERROR [WebhookProcessor] Error processing webhook job webhook-pixqrcode.paid-7435ee2f-839d-472a-ab00-5a0154076edf (pixqrcode.paid): Connection terminated unexpectedly +589ms
Error: Connection terminated unexpectedly
at /app/node_modules/.pnpm/pg-pool@3.11.0_pg@8.18.0/node_modules/pg-pool/index.js:45:11
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async PrismaPgAdapter.performIO (/app/node_modules/.pnpm/@prisma+adapter-pg@7.5.0/node_modules/@prisma/adapter-pg/dist/index.js:652:22)
at async PrismaPgAdapter.queryRaw (/app/node_modules/.pnpm/@prisma+adapter-pg@7.5.0/node_modules/@prisma/adapter-pg/dist/index.js:602:30)
at async e.interpretNode (/app/node_modules/.pnpm/@prisma+client@7.8.0_prisma@7.8.0_@types+react@19.2.10_react-dom@19.2.3_react@19.2.3__react@1_6xaps76e2xgc2so5briioy5zw4/node_modules/@prisma/client-engine-runtime/src/interpreter/query-interpreter.ts:186:26)
at async e.interpretNode (/app/node_modules/.pnpm/@prisma+client@7.8.0_prisma@7.8.0_@types+react@19.2.10_react-dom@19.2.3_react@19.2.3__react@1_6xaps76e2xgc2so5briioy5zw4/node_modules/@prisma/client-engine-runtime/src/interpreter/query-interpreter.ts:213:41)
at async e.interpretNode (/app/node_modules/.pnpm/@prisma+client@7.8.0_prisma@7.8.0_@types+react@19.2.10_react-dom@19.2.3_react@19.2.3__react@1_6xaps76e2xgc2so5briioy5zw4/node_modules/@prisma/client-engine-runtime/src/interpreter/query-interpreter.ts:272:41)
at async e.run (/app/node_modules/.pnpm/@prisma+client@7.8.0_prisma@7.8.0_@types+react@19.2.10_react-dom@19.2.3_react@19.2.3__react@1_6xaps76e2xgc2so5briioy5zw4/node_modules/@prisma/client-engine-runtime/src/interpreter/query-interpreter.ts:94:23)
at async e.execute (/app/node_modules/.pnpm/@prisma+client@7.8.0_prisma@7.8.0_@types+react@19.2.10_react-dom@19.2.3_react@19.2.3__react@1_6xaps76e2xgc2so5briioy5zw4/node_modules/@prisma/client/src/runtime/core/engines/client/LocalExecutor.ts:81:12)
at async jt.request (/app/node_modules/.pnpm/@prisma+client@7.8.0_prisma@7.8.0_@types+react@19.2.10_react-dom@19.2.3_react@19.2.3__react@1_6xaps76e2xgc2so5briioy5zw4/node_modules/@prisma/client/src/runtime/core/engines/client/ClientEngine.ts:504:22)a month ago
port: 443
},
Error: connect ENETUNREACH 2001:4860:4826:7700:::443 - Local (:::0)
at internalConnectMultiple (node:net:1206:16)
at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
errno: -101,
code: 'ENETUNREACH',
syscall: 'connect',
address: '2001:4860:4826:7700::',
port: 443
},
Error: connect ETIMEDOUT 142.251.157.119:443
at createConnectionError (node:net:1678:14)
at Timeout.internalConnectMultipleTimeout (node:net:1737:38)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
errno: -110,
code: 'ETIMEDOUT',
address: '142.251.151.119',
port: 443
syscall: 'connect',
},
address: '142.251.157.119',
port: 443
Error: connect ETIMEDOUT 142.251.151.119:443
},
Error: connect ENETUNREACH 2001:4860:4827:7700:::443 - Local (:::0)
at internalConnectMultiple (node:net:1206:16)
at createConnectionError (node:net:1678:14)
at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
at listOnTimeout (node:internal/timers:590:11)
at Timeout.internalConnectMultipleTimeout (node:net:1737:38)
at process.processTimers (node:internal/timers:523:7) {
at listOnTimeout (node:internal/timers:590:11)
errno: -101,
at process.processTimers (node:internal/timers:523:7) {
code: 'ENETUNREACH',
errno: -110,
syscall: 'connect',
code: 'ETIMEDOUT',
address: '2001:4860:4827:7700::',
port: 443
syscall: 'connect',
},
},
Error: connect ENETUNREACH 2001:4860:482a:7700:::443 - Local (:::0)
Error: connect ENETUNREACH 2001:4860:482d:7700:::443 - Local (:::0)
at internalConnectMultiple (node:net:1206:16)
at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
at internalConnectMultiple (node:net:1206:16)
at listOnTimeout (node:internal/timers:590:11)
errno: -110,
at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
at process.processTimers (node:internal/timers:523:7) {
code: 'ETIMEDOUT',
errno: -101,
syscall: 'connect',
code: 'ENETUNREACH',
address: '142.251.153.119',
syscall: 'connect',
port: 443
address: '2001:4860:482a:7700::',
port: 443
},
Error: connect ETIMEDOUT 142.251.153.119:443
at createConnectionError (node:net:1678:14)
at Timeout.internalConnectMultipleTimeout (node:net:1737:38)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
errno: -101,
code: 'ENETUNREACH',
syscall: 'connect',
address: '2001:4860:482d:7700::',
port: 443
},
Error: connect ETIMEDOUT 142.251.155.119:443
at createConnectionError (node:net:1678:14)
at Timeout.internalConnectMultipleTimeout (node:net:1737:38)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '142.251.155.119',
port: 443
},
Error: connect ENETUNREACH 2001:4860:4829:7700:::443 - Local (:::0)
at internalConnectMultiple (node:net:1206:16)
at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
errno: -101,
code: 'ENETUNREACH',
syscall: 'connect',
address: '2001:4860:4829:7700::',
port: 443
},
Error: connect ETIMEDOUT 142.251.154.119:443
at createConnectionError (node:net:1678:14)
at Timeout.internalConnectMultipleTimeout (node:net:1737:38)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '142.251.154.119',
port: 443
},
Error: connect ENETUNREACH 2001:4860:482b:7700:::443 - Local (:::0)
at internalConnectMultiple (node:net:1206:16)
at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
errno: -101,a month ago
You're refusing to make outbound requests and accept incoming connections; it seems you're having an infrastructure issue, since everything was normal until this error started early this morning. And sometimes it says that the IP address has changed and the old connections have been terminated, coming from your terminal.