2 years ago
This morning our deployment is failing. It seems as if the service can no longer access it's postgres database during the build phase. We're using the shared DATABASE_PRIVATE_URL but I've also tried using the public url.
> [stage-0 10/12] RUN pnpm run prisma:migrate:deploy:
0.924 > @ prisma:migrate:deploy /app
0.924 > prisma migrate deploy
0.924
1.468 Prisma schema loaded from prisma/schema.prisma
1.472 Datasource "db": PostgreSQL database "{redacted}", schema "public" at "postgres.railway.internal:5432"
1.552
1.553 Error: P1001: Can't reach database server at `postgres.railway.internal:5432`
1.553
1.553 Please make sure your database server is running at `postgres.railway.internal:5432`.
1.564 ELIFECYCLE Command failed with exit code 1.Sorry, I've also posted this via discord, in a bit of a panic.. Terrible timing since I have a release today!
ⓘ Deployment information is only viewable by project members and Railway employees.
2 Replies
2 years ago
it's working again now, just a temporary blip I guess.. would be nice to know what caused it thou.
2 years ago
For future reference, please do not cross post.
These are logs from the legacy builder, and that is a private domain name, the private network is not available during build on the legacy builder, you would need to be on the V2 builder to be able to communicate with services on the private network.
Status changed to Solved Railway • over 1 year ago