Issue deploying Express Backend with Postgre Prisma DB
nmufson
HOBBYOP

a year ago

Receiving logs that the container is dying quickly on deployment, but not sure if this is driving the issue. When trying to access the domain, I'm getting a 502 Bad Gateway with "Application failed to respond"

Below are my package.json scripts. I have my backend variables set to match what's in the Postgre project on my dashboard, but I think they may not be connecting properly.

 "scripts": {
    "seed": "node prisma/seed/seed.js",
    "start": "npx prisma generate && node src/app.js",
    "dev": "nodemon src/app.js"
  },

3 Replies

brody
EMPLOYEE

a year ago

Looks like you solved this by running prisma generate.


nmufson
HOBBYOP

a year ago

For some reason I am still getting a 502 Bad Gateway error, "application failed to respond". I'm not sure what's driving this issue.


brody
EMPLOYEE

a year ago

You will get 502 when the service is waking up, but beyond that, your issue is covered here -

https://docs.railway.app/guides/fixing-common-errors


Loading...