Skip to content
Generated domain returns Railway Not Found despite healthy service on 0.0.0.0:8080
m1stfly
OP

a month ago

My Railway-generated domain returns the Railway error:

“Not Found — The train has not arrived at the station.”

Project: moms-commerce-os-production

Environment: production

Service: merry-motivation

Current generated domain: merry-motivation-production-dbc7.up.railway.app

The deployment itself is healthy and Active.

Next.js 15.5.26 starts successfully and reports:

Local: http://localhost:8080

Network: http://0.0.0.0:8080

Ready

The Railway-generated domain targets port 8080.

PostgreSQL/private networking is healthy and the application can communicate with postgres.railway.internal.

HTTP Network Logs show no requests when I access or refresh the generated public domain.

I already:

  • verified the service is Active
  • verified the application listens on 0.0.0.0:8080
  • verified the generated domain targets port 8080
  • deleted and regenerated the Railway service domain
  • redeployed the service

The regenerated domain still returns Railway's own “Not Found / The train has not arrived at the station” page before the request reaches the application.

Could you please check the edge proxy/domain provisioning and the association between this generated domain and the merry-motivation service?

Solved$10 Bounty

Pinned Solution

Make sure there isn't a typo in the URL. I'd recommend you click on the link from the service settings > networking section to rule out a typo issue.

1 Reply

Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • about 1 month ago


Make sure there isn't a typo in the URL. I'd recommend you click on the link from the service settings > networking section to rule out a typo issue.


Status changed to Solved mayori • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...