23 days ago
we cant seem to open our deployed link and service is down. fix please. https://bingwaelite-production.up.railway.app/ also items in volume cannot be downloaded help. im getting ginx error. it started today but before everything was fine.
4 Replies
23 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 • 23 days ago
22 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 • 22 days ago
22 days ago
A 504 from Railway's edge usually means the platform reached your app but it didn't respond in time — so it's almost always something on the app side, not Railway itself. A few things I'd check in order:
- Deploy logs — look for crash loops, OOM kills, or unhandled exceptions right around when this started.
- Volume storage — you mentioned files in the volume won't download either. If the volume is full or hit a permissions issue, that can cause disk writes/reads to hang, which cascades into request timeouts. Worth checking free space first since it explains both symptoms at once.
- Port binding — confirm the app is listening on process.env.PORT, not a hardcoded port. Works-until-suddenly-doesn't is sometimes a redeploy that reset an env var.
- DB/external API connections — if the app is waiting on a database or third-party call that's hanging, every request queues until the gateway times out.
Start with the deploy logs — that'll usually tell you which of these it is right away.
reonfernandes
A 504 from Railway's edge usually means the platform reached your app but it didn't respond in time — so it's almost always something on the app side, not Railway itself. A few things I'd check in order: 1. Deploy logs — look for crash loops, OOM kills, or unhandled exceptions right around when this started. 2. Volume storage — you mentioned files in the volume won't download either. If the volume is full or hit a permissions issue, that can cause disk writes/reads to hang, which cascades into request timeouts. Worth checking free space first since it explains both symptoms at once. 3. Port binding — confirm the app is listening on process.env.PORT, not a hardcoded port. Works-until-suddenly-doesn't is sometimes a redeploy that reset an env var. 4. DB/external API connections — if the app is waiting on a database or third-party call that's hanging, every request queues until the gateway times out. Start with the deploy logs — that'll usually tell you which of these it is right away.
22 days ago
this actually worked to help me identify the bug. thanks alot. fixed.
22 days ago
the issue was port binding