a month ago
Hi! Our custom domain workspace.nomastudio.ai has been returning the Railway edge fallback 404 since 16/07/2026, while the service itself is healthy and reachable on its Railway-provided domain.
- Project id: cf99c959-ce7d-498d-be9e-346c38edad40 (project noma-workspace, environment production)
-
- Service: proxy (id c19bad53), target port 8080
-
- Working Railway domain: https://proxy-production-86e6.up.railway.app (HTTP 200)
-
- Failing custom domain: https://workspace.nomastudio.ai (HTTP 404)
-
- Response headers on the 404: x-railway-fallback: true, server: railway-hikari, x-railway-edge: mia1
-
- Sample request id: 5-wR3MzWRe6Ey7aWwUFZXw (17/07/2026 ~17:40 UTC, edge mia1, trace mia1.nv6z)
-
- DNS: CNAME workspace.nomastudio.ai -> kr7lggaq.up.railway.app, fully propagated
-
- Certificate status in the dashboard: VALID
Everything user-side has already been tried: re-saving the target port, multiple redeploys of the service, and deleting + re-creating the custom domain (which changed the CNAME target from k838bl37 to kr7lggaq; DNS was updated accordingly). The dashboard shows the domain and certificate as healthy, but the edge keeps serving the fallback 404, which looks like an edge routing desync on Railway's side.
Could you re-sync the edge routing for this domain? Happy to provide more request ids if useful. Thanks!
1 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
You'll have to add a TXT record for _railway-verify.workspace.nomastudio.ai containing the verification token from your project's dashboard.