Error fetching users: PrismaClientKnownRequestError: Invalid `prisma.user.findMany()` invocation in NextJs with prisma and pg. #28767

P202U · 2025-11-28T15:25:16Z

P202U
Nov 28, 2025

Question

I'm using pg local with prisma.
I'm getting this error if I go to the dashboard page:

next git:(main) ✗ pnpm run dev

[email protected] dev /home/makima/Documents/Info/next
next dev

[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: npm i baseline-browser-mapping@latest -D
▲ Next.js 16.0.5 (Turbopack)

Local: http://localhost:3000
Network: ###
Environments: .env

✓ Starting...
✓ Ready in 1528ms
○ Compiling / ...
GET / 200 in 4.4s (compile: 4.0s, render: 407ms)
GET /api/user 404 in 744ms (compile: 554ms, render: 190ms)
Error fetching users: Error [PrismaClientKnownRequestError]:
Invalid __TURBOPACK__imported__module__$5b$project$5d2f$lib$2f$prisma$2e$ts__$5b$app$2d$rsc$5d$__$28$ecmascript$29$__["default"].user.findMany() invocation in
/home/makima/Documents/Info/next/.next/dev/server/chunks/ssr/[root-of-the-server]__b87aad6c._.js:304:155

301 ;
302 async function getUsers() {
303 try {
→ 304 const users = await TURBOPACK__imported__module$5b$project$5d2f$lib$2f$prisma$2e$ts__$5b$app$2d$rsc$5d$$28$ecmascript$29$["default"].user.findMany(
Operation has timed out
at (app/api/user.ts:5:37)
at async getUsers (app/api/user.ts:5:19)
at async Dashboard (app/dashboard/page.tsx:4:17)
3 | export default async function getUsers() {
4 | try {

5 | const users = await prisma.user.findMany();
| ^
6 | console.log(users);
7 | return users;
8 | } catch (error) { {
code: 'P1008',
meta: [Object],
clientVersion: '7.0.1'
}
⨯ Error [PrismaClientKnownRequestError]:
Invalid {imported module ./lib/prisma.ts}["default"].user.findMany() invocation in
/home/makima/Documents/Info/next/.next/dev/server/chunks/ssr/[root-of-the-server]__b87aad6c._.js:304:155

301 ;
302 async function getUsers() {
303 try {
→ 304 const users = await {imported module ./lib/prisma.ts}["default"].user.findMany(
Operation has timed out
at (app/api/user.ts:5:37)
at async getUsers (app/api/user.ts:5:19)
at async Dashboard (app/dashboard/page.tsx:4:17)
3 | export default async function getUsers() {
4 | try {

5 | const users = await prisma.user.findMany();
| ^
6 | console.log(users);
7 | return users;
8 | } catch (error) { {
code: 'P1008',
meta: [Object],
clientVersion: '7.0.1',
digest: '3171616793'
}
GET /dashboard 500 in 2.3min (compile: 832ms, render: 2.3min)
Warning: 'ozone-platform-hint' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'gtk-version' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'ignore-gpu-blocklist' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'enable-wayland-ime' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'ozone-platform-hint' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'gtk-version' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'ignore-gpu-blocklist' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'enable-wayland-ime' is not in the list of known options, but still passed to Electron/Chromium.
^C[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: npm i baseline-browser-mapping@latest -D

users.ts:
import prisma from '@/lib/prisma';

async function getUsers() {
try {
console.log('Fetching users...');
const users = await prisma.user.findMany();
console.log('Users fetched:', users);
return users;
} catch (error) {
console.error('Error fetching users:', error);
throw error;
}
}
getUsers();

dashboard.page.tsx:
import getUsers from '../api/user';

export default async function Dashboard() {
const users = await getUsers();
return (

  <h1 className="text-4xl font-bold mb-8 font-(family-name:--font-geist-sans) text-[#333333]">
    Users
  </h1>
  <ol className="list-decimal list-inside font-(family-name:--font-geist-sans)">
    {users.map(user => (
      <li key={user.id} className="mb-2">
        {user.name} {user.email}
      </li>
    ))}
  </ol>
</div>

);
}

info=# SELECT * from "User";
id | email | name |
password | createdAt |
updatedAt
--------------------------------------+-----------------+-------+----------------------------------
-----------------------------------------------------------------+-------------------------+-------

And if I change user.ts a bit:
import prisma from '@/lib/prisma';

async function getUsers() {
try {
console.log('Fetching users...');
const users = await prisma.user.findMany();
console.log('Users fetched:', users);
return users;
} catch (error) {
console.error('Error fetching users:', error);
throw error;
}
}
getUsers();

And run: pnpm tsx ./app/api/user.ts
Then I get:
Fetching users...
Error fetching users: PrismaClientKnownRequestError:
Invalid prisma.user.findMany() invocation in
/home/makima/Documents/Info/next/app/api/user.ts:6:37

3 async function getUsers() {
4 try {
5 console.log('Fetching users...');
→ 6 const users = await prisma.user.findMany(
The table public.User does not exist in the current database.
at $r.handleRequestError (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client/src/runtime/RequestHandler.ts:228:13)
at $r.handleAndLogRequestError (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client/src/runtime/RequestHandler.ts:174:12)
at $r.request (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client/src/runtime/RequestHandler.ts:143:12)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async a (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client/src/runtime/getPrismaClient.ts:766:24)
at async getUsers (/home/makima/Documents/Info/next/app/api/user.ts:6:19) {
code: 'P2021',
meta: {
modelName: 'User',
driverAdapterError: DriverAdapterError: TableDoesNotExist
at PrismaPgAdapter.onError (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]/node_modules/@prisma/adapter-pg/dist/index.js:693:11)
at PrismaPgAdapter.performIO (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]/node_modules/@prisma/adapter-pg/dist/index.js:688:12)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async PrismaPgAdapter.queryRaw (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]/node_modules/@prisma/adapter-pg/dist/index.js:608:30)
at async (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client-engine-runtime/src/tracing.ts:68:22)
at async mr (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client-engine-runtime/src/tracing.ts:56:10)
at async e.interpretNode (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client-engine-runtime/src/interpreter/query-interpreter.ts:175:26)
at async e.interpretNode (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client-engine-runtime/src/interpreter/query-interpreter.ts:261:41)
at async e.run (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client-engine-runtime/src/interpreter/query-interpreter.ts:83:23)
at async e.execute (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client/src/runtime/core/engines/client/LocalExecutor.ts:75:12) {
cause: [Object]
}
},
clientVersion: '7.0.1'
}
node:internal/process/promises:394
triggerUncaughtException(err, true /* fromPromise */);
^

PrismaClientKnownRequestError:
Invalid prisma.user.findMany() invocation in
/home/makima/Documents/Info/next/app/api/user.ts:6:37

3 async function getUsers() {
4 try {
5 console.log('Fetching users...');
→ 6 const users = await prisma.user.findMany(
The table public.User does not exist in the current database.
at $r.handleRequestError (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client/src/runtime/RequestHandler.ts:228:13)
at $r.handleAndLogRequestError (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client/src/runtime/RequestHandler.ts:174:12)
at $r.request (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client/src/runtime/RequestHandler.ts:143:12)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async a (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client/src/runtime/getPrismaClient.ts:766:24)
at async getUsers (/home/makima/Documents/Info/next/app/api/user.ts:6:19) {
code: 'P2021',
meta: {
modelName: 'User',
driverAdapterError: DriverAdapterError: TableDoesNotExist
at PrismaPgAdapter.onError (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]/node_modules/@prisma/adapter-pg/dist/index.js:693:11)
at PrismaPgAdapter.performIO (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]/node_modules/@prisma/adapter-pg/dist/index.js:688:12)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async PrismaPgAdapter.queryRaw (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]/node_modules/@prisma/adapter-pg/dist/index.js:608:30)
at async (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client-engine-runtime/src/tracing.ts:68:22)
at async mr (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client-engine-runtime/src/tracing.ts:56:10)
at async e.interpretNode (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client-engine-runtime/src/interpreter/query-interpreter.ts:175:26)
at async e.interpretNode (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client-engine-runtime/src/interpreter/query-interpreter.ts:261:41)
at async e.run (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client-engine-runtime/src/interpreter/query-interpreter.ts:83:23)
at async e.execute (/home/makima/Documents/Info/next/node_modules/.pnpm/@prisma [email protected]_prisma@7.0.1_@types [email protected]_react-dom@[email protected]__re_6bc95346ce983164bf43b9b4fbc1fdfe/node_modules/@prisma/client/src/runtime/core/engines/client/LocalExecutor.ts:75:12) {
cause: {
originalCode: '42P01',
originalMessage: 'relation "public.User" does not exist',
kind: 'TableDoesNotExist',
table: 'public.User'
}
}
},
clientVersion: '7.0.1'
}

Node.js v22.18.0

Also:

next git:(main) ✗ pnpm dlx prisma generate
Loaded Prisma config from prisma.config.ts.

Prisma schema loaded from prisma/schema.prisma

✔ Generated Prisma Client (7.0.1) to ./generated/prisma in 86ms

next git:(main) ✗ pnpm dlx prisma migrate dev
Loaded Prisma config from prisma.config.ts.

Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "info", schema "public" at "localhost:5432"

Already in sync, no schema change or pending migration was found.
And studio also shows that there's a seeded User table.

Any idea how to resolve this?

How to reproduce (optional)

Follow this: https://www.prisma.io/docs/guides/nextjs
Except schema is different and I use pnpm.

Expected behavior (optional)

It should fetch without problem.

Information about Prisma Schema, Client Queries and Environment (optional)

generator client {
  provider = "prisma-client"
  output   = "../generated/prisma"
}

datasource db {
  provider = "postgresql"
}

model User {
  id        String   @id @default(uuid())
  email     String   @unique
  name      String?
  password  String
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
}

OS: Arch Linux
Database: PostgresSQL 18.1
Node.js version: v22.18.0
prisma : 7.0.1
@prisma/client : 7.0.1

prisma.config.ts

// This file was generated by Prisma and assumes you have installed the following:
// npm install --save-dev prisma dotenv
import 'dotenv/config';
import { defineConfig, env } from 'prisma/config';

export default defineConfig({
  schema: 'prisma/schema.prisma',
  migrations: {
    path: 'prisma/migrations',
    seed: `tsx prisma/seed.ts`,
  },
  datasource: {
    url: env('DATABASE_URL'),
  },
});

seed.ts

import { PrismaClient, Prisma } from '@/generated/prisma/client';
import { PrismaPg } from '@prisma/adapter-pg';
import 'dotenv/config';
import argon2 from 'argon2';

const adapter = new PrismaPg({
  connectionString: process.env.DATABASE_URL,
});

const prisma = new PrismaClient({
  adapter,
});

const adminPassword = process.env.ADMIN_PASSWORD;
const adminEmail = process.env.ADMIN_EMAIL;

if (!adminPassword) {
  throw new Error(
    'ADMIN_PASSWORD environment variable is missing. Please set it in your .env file.'
  );
}

if (!adminEmail) {
  throw new Error(
    'ADMIN_EMAIL environment variable is missing. Please set it in your .env file.'
  );
}

const userData: Prisma.UserCreateInput[] = [
  {
    name: 'Admin',
    email: adminEmail,
    password: adminPassword,
  },
  {
    name: 'Bob',
    email: '[email protected]',
    password: 'password456',
  },
];

export async function main() {
  for (const u of userData) {
    const hashedPassword = await argon2.hash(u.password);

    await prisma.user.create({
      data: {
        email: u.email,
        name: u.name,
        password: hashedPassword,
      },
    });
  }
}

main()
  .catch(e => {
    console.error('Error seeding the database:', e);
    process.exit(1);
  })
  .finally(async () => {
    await prisma.$disconnect();
  });

nishatislam04 · 2025-11-29T15:59:08Z

nishatislam04
Nov 29, 2025

first why it is 404
GET /api/user 404 in 744ms (compile: 554ms, render: 190ms)
and i can see this message accross the logs multiple times
The table public.User does not exist in the current database.

are you using local prisma postgres instance or cloud prisma postgres?

1 reply

P202U Nov 30, 2025
Author

/api/user was just frustation. That's not a route so it's fine.
And yeah I'm using PostgresSQL 18.1 local.
And that's the whole problem.
It was seeded just fine and even psql and prisma studio says so but when I try to run any prisma query, this error follows.

cleverlight · 2025-12-01T08:11:40Z

cleverlight
Dec 1, 2025

It might be worth checking your SSL config. I found that the command line (e.g. pnpm dlx prisma generate) was much more lenient than the PG adapter, so it could be something like your localhost SSL config contains a self-signed cert, which is rejected by default.

This code tells the PG client not to worry about checking the Postgres server's SSL/TLS cert. This isn't recommended for production, but for localhost/dev it would at least verify that SSL handshaking is the problem.

const adapter = new PrismaPg({
  connectionString: process.env.DATABASE_URL,
  ssl: {
    rejectUnauthorized: false,
  },
});

const prisma = new PrismaClient({
  adapter,
});

4 replies

nurul3101 Dec 2, 2025
Maintainer

Did this help?

Are you still seeing the same issue?

P202U Dec 3, 2025
Author

Yup.
I'm still seeing it.
Downgrade. It works fine that way.

P202U Dec 3, 2025
Author

But I still appreciate any suggestions.
Wanna see this issue resolved.

nurul3101 Dec 10, 2025
Maintainer

Can you provide a minimal reproduction so that I can investigate what's causing the issue?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Error fetching users: PrismaClientKnownRequestError: Invalid `prisma.user.findMany()` invocation in NextJs with prisma and pg. #28767

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 2 comments 5 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Error fetching users: PrismaClientKnownRequestError: Invalid prisma.user.findMany() invocation in NextJs with prisma and pg. #28767

Uh oh!

Uh oh!

P202U Nov 28, 2025

Question

info=# SELECT * from "User"; id | email | name | password | createdAt | updatedAt --------------------------------------+-----------------+-------+---------------------------------- -----------------------------------------------------------------+-------------------------+-------

How to reproduce (optional)

Expected behavior (optional)

Information about Prisma Schema, Client Queries and Environment (optional)

Replies: 2 comments · 5 replies

Uh oh!

nishatislam04 Nov 29, 2025

Uh oh!

Uh oh!

P202U Nov 30, 2025 Author

Uh oh!

cleverlight Dec 1, 2025

Uh oh!

nurul3101 Dec 2, 2025 Maintainer

Uh oh!

P202U Dec 3, 2025 Author

Uh oh!

P202U Dec 3, 2025 Author

Uh oh!

nurul3101 Dec 10, 2025 Maintainer

Error fetching users: PrismaClientKnownRequestError: Invalid `prisma.user.findMany()` invocation in NextJs with prisma and pg. #28767

P202U
Nov 28, 2025

info=# SELECT * from "User";
id | email | name |
password | createdAt |
updatedAt
--------------------------------------+-----------------+-------+----------------------------------
-----------------------------------------------------------------+-------------------------+-------

Replies: 2 comments 5 replies

nishatislam04
Nov 29, 2025

P202U Nov 30, 2025
Author

cleverlight
Dec 1, 2025

nurul3101 Dec 2, 2025
Maintainer

P202U Dec 3, 2025
Author

P202U Dec 3, 2025
Author

nurul3101 Dec 10, 2025
Maintainer