Subject: Railway-provided domain returns “The train has not arrived at the station” while service is healthy

Hi Railway team,

I have a service named surebet-app that is healthy and passes internal healthchecks, but the Railway-provided public domain always returns the Railway 404 page:

“Not Found

The train has not arrived at the station.

Please check your network settings to confirm that your domain has provisioned.”

Project/service details:

• Service: surebet-app
• Public domain: https://surebet-app.up.railway.app
• Latest active deployment: 9d57dd68-84b8-4dd6-b7fa-2b23627e3607
• Earlier deployment after domain port binding test: e6adeb65-1d8e-4094-9462-5b5a288cc97b

What I already verified:

• Service status is ONLINE
• Deployment status is SUCCESS
• App listens on 0.0.0.0:8080
• Internal Railway healthcheck hits /health and gets 200 OK
• PostgreSQL is connected and the app completes startup
• I removed and regenerated the Railway-provided domain
• I redeployed after networking changes
• I also tested binding the public domain to port 8080

Evidence:

• Runtime logs show:

  • Application startup complete
  • Uvicorn running on http://0.0.0.0:8080
  • GET /health 200 OK from Railway internal IP

• Public HTTP logs show no incoming public requests

• Browser shows Railway edge page:

  “The train has not arrived at the station”

This suggests the app is healthy internally, but the Railway public domain is not routing traffic to the service.

Could you please verify:

1. whether the Railway-provided domain is correctly provisioned and attached to the active deployment,
2. whether edge/public networking is routing to this service,
3. whether there is any issue with domain provisioning or networking control plane for this project/service.

I can provide screenshot evidence of the Railway 404 page if needed.