Pinned Solution
12 days ago
Did you set the DATABASE_URL variable in your service?
Also, make sure to redeploy after adding the variable.
4 Replies
12 days ago
Having looked into this, the issue appears to be in your application code or configuration rather than the Railway platform itself, which puts it outside what Railway support can resolve directly.
This is exactly the kind of problem the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.
Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.
- Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
- Keep it private and close the thread - Nothing becomes public and the thread closes.
Status changed to Awaiting User Response Railway • 12 days ago
12 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 12 days ago
mayori
Can you share the error message on your Deploy Logs?
12 days ago
Error: DATABASE_URL must be set. Did you forget to provision a database?
12 days ago
Did you set the DATABASE_URL variable in your service?
Also, make sure to redeploy after adding the variable.
Status changed to Solved mayori • 12 days ago