a month ago
Newly created services never get public edge routing; pre-existing services work fine. Since ~2026-07-05, any new service+domain in my account returns 502 with x-railway-fallback: true (server: railway-hikari) - including traefik/whoami probes - while services created earlier keep routing normally. Verified: it happens in brand-new projects AND when adding a new service to an old, working project; in both europe-west and us-west2; deployments are SUCCESS; containers verified healthy from inside (correct port, IPv4+IPv6); private networking works; domain targetPort correct; zero requests reach containers (no access logs).
5 Replies
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
a month ago
Try redeploying your service.
An online deployment should show "Online" instead of "Success."
a month ago
Hi!
Thanks for taking the time to reply!
The deployment is “Online”, but navigating to the public networking address response with 502 status code.
Any recommendations for investigation something?
a month ago
I'd try setting the port to an arbitrary number (eg, 4100) and change the port on the URL as well, then redeploy.
a month ago
why does that matter?
In this deployment, it’s a uvicorn and the port was selected to be 8000.
a month ago
Just arbitrary debugging steps 🤷♂️.
Also, make sure uvicorn is listening on 0.0.0.0 instead of localhost or something else.