[Nest] 73 - 05/12/2026, 4:44:41 PM ERROR [AllExceptionsFilter] GET /api/settings/visual-config → 500

at async Promise.all (index 0)

at async SettingsService.getVisualConfig (/app/dist/main.js:7024:72)

prisma:error

Invalid prisma.settings.findUnique() invocation:

at $n.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:6623)

at async Promise.all (index 0)

[Nest] 73 - 05/12/2026, 4:44:42 PM DEBUG [AppWebSocketGateway] [Device Heartbeat] Failed to update device browser-be4b5c9d-a61e-4810-8998-6a30056decbf:

Invalid prisma.userDevice.updateMany() invocation:

prisma:error

Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 33)

prisma:error

prisma:error

Invalid prisma.settings.findUnique() invocation:

Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 33)

Invalid prisma.settings.findUnique() invocation:

at async Promise.all (index 0)

at async LocalStrategy.callback [as _verify] (/app/node_modules/@nestjs/passport/dist/passport/passport.strategy.js:11:44)

[Nest] 73 - 05/12/2026, 4:44:43 PM ERROR [AllExceptionsFilter] POST /api/auth/login → 500

at $n.request (/app/node_modules/@prisma/client/runtime/library.js:121:6307)

Executará em: 2026-05-12T16:44:58.260Z

Invalid prisma.userDevice.updateMany() invocation:

PrismaClientKnownRequestError:

Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 33)

at $n.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7315)

Invalid prisma.userDevice.updateMany() invocation:

prisma:error

Invalid prisma.user.findUnique() invocation:

Invalid prisma.user.findUnique() invocation:

Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 33)

at $n.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7315)

at $n.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:6623)

at $n.request (/app/node_modules/@prisma/client/runtime/library.js:121:6307)

at async AuthService.validateUser (/app/dist/main.js:769:22)

[Nest] 73 - 05/12/2026, 4:44:43 PM ERROR [AppWebSocketGateway] Connection error: jwt expired

Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 33)

prisma:error

Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 33)

prisma:error

[Nest] 73 - 05/12/2026, 4:44:43 PM ERROR [AllExceptionsFilter] GET /api/settings/visual-config → 500

PrismaClientKnownRequestError:

Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 33)

at $n.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7315)

at async l (/app/node_modules/@prisma/client/runtime/library.js:130:9633)

at async Promise.all (index 0)

Invalid prisma.settings.findUnique() invocation:

2026-05-12 15:57:50.012 UTC [5254] ERROR: could not serialize access due to concurrent update

2026-05-12 15:57:50.012 UTC [5254] STATEMENT:

SELECT "family_id" AS "familyId"

FROM "refresh_tokens"

WHERE "id" = $1

FOR UPDATE

2026-05-12 16:00:00.369 UTC [35] LOG: checkpoint complete: wrote 2181 buffers (13.3%); 0 WAL file(s) added, 0 removed, 1 recycled; write=220.205 s, sync=0.158 s, total=220.783 s; sync files=81, longest=0.069 s, average=0.002 s; distance=15026 kB, estimate=18007 kB; lsn=F/BE9208B8, redo lsn=F/BDBBACA0

2026-05-12 16:00:03.191 UTC [5274] ERROR: could not serialize access due to concurrent update

2026-05-12 16:00:03.191 UTC [5274] STATEMENT:

SELECT "family_id" AS "familyId"

FROM "refresh_tokens"

WHERE "id" = $1

FOR UPDATE

2026-05-12 16:00:54.623 UTC [5280] ERROR: could not serialize access due to concurrent update

2026-05-12 16:00:54.623 UTC [5280] STATEMENT:

SELECT "family_id" AS "familyId"

FROM "refresh_tokens"

WHERE "id" = $1

FOR UPDATE

2026-05-12 16:01:19.448 UTC [35] LOG: checkpoint starting: time

FROM "refresh_tokens"

WHERE "id" = $1

FOR UPDATE

2026-05-12 16:02:37.243 UTC [5285] ERROR: could not serialize access due to concurrent update

2026-05-12 16:02:37.243 UTC [5285] STATEMENT:

SELECT "family_id" AS "familyId"

2026-05-12 16:05:35.506 UTC [35] LOG: checkpoint complete: wrote 2535 buffers (15.5%); 0 WAL file(s) added, 0 removed, 1 recycled; write=255.778 s, sync=0.044 s, total=256.058 s; sync files=60, longest=0.015 s, average=0.001 s; distance=17441 kB, estimate=17950 kB; lsn=F/BFCB3E08, redo lsn=F/BECC3358

2026-05-12 16:06:19.550 UTC [35] LOG: checkpoint starting: time

2026-05-12 16:10:33.601 UTC [35] LOG: checkpoint complete: wrote 2356 buffers (14.4%); 0 WAL file(s) added, 0 removed, 1 recycled; write=253.881 s, sync=0.078 s, total=254.052 s; sync files=83, longest=0.025 s, average=0.001 s; distance=17852 kB, estimate=17940 kB; lsn=F/C11E6D30, redo lsn=F/BFE32468

2026-05-12 16:11:19.646 UTC [35] LOG: checkpoint starting: time

2026-05-12 16:14:37.361 UTC [5380] ERROR: could not serialize access due to concurrent update

2026-05-12 16:14:37.361 UTC [5380] STATEMENT:

SELECT "family_id" AS "familyId"

FROM "refresh_tokens"

WHERE "id" = $1

FOR UPDATE

2026-05-12 16:15:26.739 UTC [35] LOG: checkpoint complete: wrote 2082 buffers (12.7%); 0 WAL file(s) added, 0 removed, 2 recycled; write=246.762 s, sync=0.104 s, total=247.094 s; sync files=71, longest=0.031 s, average=0.002 s; distance=21970 kB, estimate=21970 kB; lsn=F/C2636E68, redo lsn=F/C13A6CC0

2026-05-12 16:16:19.791 UTC [35] LOG: checkpoint starting: time

2026-05-12 16:20:14.776 UTC [35] LOG: checkpoint complete: wrote 1870 buffers (11.4%); 0 WAL file(s) added, 0 removed, 1 recycled; write=234.653 s, sync=0.112 s, total=234.986 s; sync files=82, longest=0.056 s, average=0.002 s; distance=22072 kB, estimate=22072 kB; lsn=F/C3C1CDC8, redo lsn=F/C2935018

2026-05-12 16:21:19.838 UTC [35] LOG: checkpoint starting: time

2026-05-12 16:25:33.723 UTC [35] LOG: checkpoint complete: wrote 1806 buffers (11.0%); 0 WAL file(s) added, 0 removed, 2 recycled; write=253.425 s, sync=0.089 s, total=253.885 s; sync files=130, longest=0.027 s, average=0.001 s; distance=24133 kB, estimate=24133 kB; lsn=F/C539FDA0, redo lsn=F/C40C6698

2026-05-12 16:26:19.772 UTC [35] LOG: checkpoint starting: time

2026-05-12 16:26:40.064 UTC [5464] ERROR: could not serialize access due to read/write dependencies among transactions

2026-05-12 16:26:40.064 UTC [5464] DETAIL: Reason code: Canceled on commit attempt with conflict in from prepared pivot.

2026-05-12 16:26:40.064 UTC [5464] HINT: The transaction might succeed if retried.

2026-05-12 16:26:40.064 UTC [5464] STATEMENT: COMMIT

2026-05-12 16:26:40.066 UTC [5464] WARNING: there is no transaction in progress

2026-05-12 16:26:41.101 UTC [5471] ERROR: could not serialize access due to read/write dependencies among transactions

2026-05-12 16:26:41.101 UTC [5471] DETAIL: Reason code: Canceled on commit attempt with conflict in from prepared pivot.

2026-05-12 16:26:41.101 UTC [5471] HINT: The transaction might succeed if retried.

2026-05-12 16:26:41.101 UTC [5471] STATEMENT: COMMIT

2026-05-12 16:26:41.103 UTC [5471] WARNING: there is no transaction in progress

2026-05-12 16:26:43.850 UTC [5456] ERROR: could not serialize access due to read/write dependencies among transactions

2026-05-12 16:26:43.850 UTC [5456] DETAIL: Reason code: Canceled on commit attempt with conflict in from prepared pivot.

2026-05-12 16:26:43.850 UTC [5456] HINT: The transaction might succeed if retried.

2026-05-12 16:26:43.850 UTC [5456] STATEMENT: COMMIT

2026-05-12 16:26:43.851 UTC [5456] WARNING: there is no transaction in progress

2026-05-12 16:32:17.898 UTC [5463] WARNING: there is no transaction in progress

2026-05-12 16:32:17.899 UTC [5467] WARNING: there is no transaction in progress

2026-05-12 16:32:17.899 UTC [5448] WARNING: there is no transaction in progress

2026-05-12 16:32:17.900 UTC [5451] WARNING: there is no transaction in progress

2026-05-12 16:32:17.908 UTC [5461] WARNING: there is no transaction in progress

2026-05-12 16:34:36.297 UTC [5517] ERROR: canceling statement due to statement timeout

2026-05-12 16:34:36.297 UTC [5517] STATEMENT: /* railway:dataui / SET statement_timeout = '30s'; / railway:dataui */ SELECT table_name FROM information_schema.tables WHERE table_schema = 'public'

2026-05-12 16:34:36.297 UTC [5517] LOG: could not send data to client: Broken pipe

2026-05-12 16:34:36.297 UTC [5517] FATAL: connection to client lost

2026-05-12 16:34:46.396 UTC [5520] ERROR: canceling statement due to statement timeout

2026-05-12 16:34:46.396 UTC [5520] STATEMENT: /* railway:dataui / SET statement_timeout = '30s'; / railway:dataui */ SELECT table_name FROM information_schema.tables WHERE table_schema = 'public'

2026-05-12 16:35:16.693 UTC [5522] ERROR: canceling statement due to statement timeout

2026-05-12 16:35:16.693 UTC [5522] STATEMENT: /* railway:dataui / SET statement_timeout = '30s'; / railway:dataui */ SELECT schema_name FROM information_schema.schemata WHERE schema_name NOT IN ('pg_catalog', 'information_schema', 'pg_toast') ORDER BY schema_name

2026-05-12 16:35:37.279 UTC [5526] ERROR: canceling statement due to statement timeout

2026-05-12 16:35:37.279 UTC [5526] STATEMENT: /* railway:dataui / SET statement_timeout = '30s'; / railway:dataui */ SELECT table_name FROM information_schema.tables WHERE table_schema = 'public'

2026-05-12 16:35:37.280 UTC [5526] LOG: could not send data to client: Broken pipe

2026-05-12 16:35:37.280 UTC [5526] FATAL: connection to client lost

2026-05-12 16:44:18.402 UTC [5540] ERROR: canceling statement due to statement timeout

2026-05-12 16:44:18.402 UTC [5540] STATEMENT: /* railway:dataui / SET statement_timeout = '30s'; / railway:dataui */ SELECT table_name FROM information_schema.tables WHERE table_schema = 'public'

2026-05-12 16:44:18.402 UTC [5540] LOG: could not send data to client: Broken pipe

2026-05-12 16:44:18.402 UTC [5540] FATAL: connection to client lost

2026-05-12 16:45:14.968 UTC [5544] ERROR: canceling statement due to statement timeout

2026-05-12 16:45:14.968 UTC [5544] STATEMENT: /* railway:dataui / SET statement_timeout = '30s'; / railway:dataui */ SELECT table_name FROM information_schema.tables WHERE table_schema = 'public'

2026-05-12 16:45:14.968 UTC [5544] LOG: could not send data to client: Broken pipe

2026-05-12 16:45:14.968 UTC [5544] FATAL: connection to client lost

same

Restarting the backend and Postgre won't help!

Error: P1001: Can't reach database server at postgres.railway.internal:5432

Please make sure your database server is running at postgres.railway.internal:5432.

Please make sure your database server is running at postgres.railway.internal:5432.

Prisma schema loaded from prisma/schema.prisma

Datasource "db": PostgreSQL database "railway", schema "public" at "postgres.railway.internal:5432"

Error: P1001: Can't reach database server at postgres.railway.internal:5432

Prisma schema loaded from prisma/schema.prisma

Datasource "db": PostgreSQL database "railway", schema "public" at "postgres.railway.internal:5432"

Error: P1001: Can't reach database server at postgres.railway.internal:5432

Please make sure your database server is running at postgres.railway.internal:5432.

can you guys try enable Outbound IPv6 on the backend service? i just encounter this error hours ago and fixed after enabling it