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

mulepiemmasonTRIAL

3 months ago

Build log:

"npm ci" did not complete successfully: exit code: 1

View in context

npm warn config production Use --omit=dev instead.

osems@1.0.0 postinstall
(prisma generate --schema=./prisma/schema.postgres.prisma) && (prisma migrate deploy --schema=./prisma/schema.postgres.prisma) && (npm run installer)

Prisma schema loaded from prisma/schema.postgres.prisma

✔ Generated Prisma Client (4.15.0 | library) to ./node_modules/@prisma/client in 138ms
You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()

Prisma schema loaded from prisma/schema.postgres.prisma

Datasource "db": PostgreSQL database "railway" 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.

View Deploy details

ⓘ Deployment information is only viewable by project members and Railway employees.

1 Replies

3 months ago

Hello,

The private network is not available during build time, you would instead want to perform all database related tasks during pre-deploy -

https://docs.railway.com/guides/pre-deploy-command

Best,

Brody


Can't reach database server at `postgres.railway.internal`:`5432` - Railway Help Station