a month ago
Hi team,
My custom domain www.uorky.com consistently returns the Railway "Application not found" / "The train has not arrived at the station" 404 page, even though everything on the configuration side is green.
Project: uorky · Service: uorky · Environment: production
Custom domain: www.uorky.com → CNAME target 4duvn0lu.up.railway.app
The Railway dashboard shows: certificate status VALID, DNS record PROPAGATED, and currentValue == requiredValue.
The active deployment even reports staticUrl: www.uorky.com with status SUCCESS.
The service's own *.up.railway.app domain works perfectly (HTTP 200); only the custom domain 404s.
DNS is correct at the authoritative nameservers (ns33/ns34.domaincontrol.com) and at public resolvers (1.1.1.1, 8.8.8.8), all returning the correct target.
Things I already tried, all with the same result: deleting and recreating the custom domain (multiple times, waiting ~8 min between delete and recreate for the edge to release the record), forcing certificate issuance (customDomainIssueCertificate), setting the custom domain's targetPort to auto to match the working service domain, and redeploying.
The domain was originally added on a different Railway account and later moved to this one — I suspect a stale edge/routing record for www.uorky.com is preventing the new binding from routing. Could you please clear/investigate the edge routing for this hostname so it attaches to the service?
Thanks!
3 Replies
a month 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 • about 1 month ago
a month ago
You mention that "the native *.up.railway.app domain works" but I don't think that's the case. Both www.uorky.com and 4duvn0lu.up.railway.app bring you to your 404 screen.
Both return the same thing (Railway's edge fallback):
HTTP 404 {"status":"error","code":404,"message":"Application not found"}
x-railway-fallback: true
x-railway-fallback: true means the request reached Railway's edge fine, but there's no active deployment for it to route to. Since your native domain returns it too, this cant be a custom domain problem.
This also rules out everything you've tried so far. DNS is correct (www.uorky.com → CNAME → 4duvn0lu.up.railway.app → 69.46.46.99 (Railway)). Your cert is fine and seems to be fresh. The edge can only serve that cert if the domain is properly bound to your service so it cant be "stale record from the old account".
The actual issue is that your service has no active/healthy deployment, so the edge has nothing to serve and every domain on it 404s.
Please check:
- Is there an Active deployment? If the latest is Crashed/Removed/Failed, that's your problem right there.
- If it crashed, open the deploy logs. Its likely a startup crash (ex: bad start command, port binding, or missing env var).
The moment a deployment is healthy and running, both domains will work with no domain changes.
a month ago
You need to add a TXT record for _railway-verify.www.uorky.com. If you are using the API to add your custom domain, you can find it in verificationToken under status.