Question

I am new to prisma and have no idea how to fix this problem, an unusual issue:

export const prisma = remember('prisma', () => {
  const connectionString = ${process.env.DATABASE_URL};
  const adapter = new PrismaPg({ connectionString });

  const client = new PrismaClient({
    adapter,
  });
  void client.$connect();
  return client;
});

when I run npx prisma migrate deploy, DB is migrated and the tables are created. but when I run the app, the client gives me following error: User was denied access on the database <container_ip>. Error: P1010. With the same connection url string for client and migration, why the client is using <container_ip>?

In prisma debug mode the logs are following, despite correct connectionString in adapter somehow the database name is overwritten with localhost IP

PrismaPgAdapterFactory {
  provider: 'postgres',
  adapterName: '@prisma/adapter-pg',
  config: {
    connectionString: 'postgresql://test:<redacted-password>@<db-url>:5432/test?schema=test\n'
  },
  options: undefined
}

prisma:client:request_handler {
  "code": "P1010",
  "meta": {
    "database_name": "<container_ip>"
  },
  "clientVersion": "6.7.0",
  "name": "PrismaClientKnownRequestError"
}

I manually ran npx prisma generate in the container, it found the env variables and loaded them and it did its job. Then I tried to run the client, the output was:

prisma:tryLoadEnv Environment variables not found at null +8ms
prisma:tryLoadEnv Environment variables loaded from /app/.env +1ms
postgresql://test:<redacted-password>@<db-url>:5432/test?schema=test

and even then the error still persists: User was denied access on the database <container_ip>

How to reproduce (optional)

This issue is happening in a container running on remote host, trying to get it running in a kuberenetes cluster. On local machine it is working correctly. Created a container with a schema and a client app. The schema responds to npx prisma command but the client code throws the error.

Expected behavior (optional)

No response

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

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["typedSql", "driverAdapters"]
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model User {
  id          String  @id @default(cuid())
  email       String  @unique
  username    String  @unique
  name        String
  mobile      String
  countryCode String
  active      Boolean

  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt

  password    Password?
  notes       Note[]
  roles       Role[]
}

prisma:client {
  "modelName": "User",
  "action": "findUnique",
  "query": {
    "arguments": {
      "where": {
        "username": "[email protected]"
      }
    },
    "selection": {
      "id": true,
      "active": true,
      "password": {
        "arguments": {},
        "selection": {
          "hash": true
        }
      }
    }
  }
}

• OS: Debian GNU/Linux 12 (bookworm)

• Database: PostgreSQL

• Node.js version: v22.16.0

• Run prisma -v to see your Prisma version and paste it
  prisma : 6.10.0
  @prisma/client : 6.10.0
  Computed binaryTarget : debian-openssl-3.0.x
  Operating System : linux
  Architecture : x64
  Node.js : v22.16.0
  TypeScript : unknown
  Query Engine (Node-API) : libquery-engine aee10d5a411e4360c6d3445ce4810ca65adbf3e8 (at node_modules/@prisma/engines/libquery_engine-debian-openssl-3.0.x.so.node)
  PSL : @prisma/prisma-schema-wasm 6.10.0-43.aee10d5a411e4360c6d3445ce4810ca65adbf3e8
  Schema Engine : schema-engine-cli aee10d5a411e4360c6d3445ce4810ca65adbf3e8 (at node_modules/@prisma/engines/schema-engine-debian-openssl-3.0.x)
  Default Engines Hash : aee10d5a411e4360c6d3445ce4810ca65adbf3e8
  Studio : 0.511.0
  Preview Features : driverAdapters, typedSql