Custom domain www stuck at edge fallback 404 despite propagated DNS + valid issued cert (3rd recreated object, same symp
minimumviablehuman
HOBBYOP

a month ago

Project b5847ebf-0830-4774-934d-083e7e5393cd, environment 8edc0690-8ecb-45f6-8192-f9e1818b2355, service c0fcbdc1-502a-4919-af48-bb2d531fb2b5 (edge: ord1).

https://www.minimumviablehuman.ca returns the Railway fallback page (404, x-railway-fallback: true, "the train has not arrived at the station") on every request. Example request IDs: B9_E5AKSQXKylAM-Y53eZw, vjL9hWx4RWi6wOpOnPRhug, fix6QGfBT6enquGWjq4OvQ.

Everything the checklist covers is green:

  • Custom domain object 03769bb7-77b9-4670-aa0d-7795c6b3656f (created 2026-07-06 21:10 UTC): the API reports the CNAME (www3girn9x9.up.railway.app) as DNS_RECORD_STATUS_PROPAGATED, and public resolvers agree.
  • TLS is fine: after customDomainIssueCertificate, the cert for www.minimumviablehuman.ca issued (valid to 2026-10-04) and is what the edge now serves. Only HTTP routing falls through to fallback.
  • The apex custom domain minimumviablehuman.ca on the same service serves 200 normally, as does the service domain minimum-viable-human-production.up.railway.app. Both domain objects have identical config (targetPort: null).

History: this is the third incarnation of the www domain object since 2026-07-05 — deleting and recreating the object cleared the identical symptom before, but it keeps returning, so the recreate loop looks like symptom treatment. A fresh redeploy (deployment 8d6e4888-12f5-4bf9-be2c-f16d2b87adfa, SUCCESS) also did not clear it; example post-deploy request: YK0lqZcOQEuJxiRUljLL4A. Could you take a look at the edge route registration for this hostname? Happy to provide anything else.

Solved$10 Bounty

Pinned Solution

You need to add a TXT record for _railway-verify.www.minimumviablehuman.ca. If you are using the API to add your custom domain, you can find it in verificationToken under status.

2 Replies

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 2 months ago


You need to add a TXT record for _railway-verify.www.minimumviablehuman.ca. If you are using the API to add your custom domain, you can find it in verificationToken under status.


minimumviablehuman
HOBBYOP

a month ago

That was it — the API's status.verificationToken needed a TXT at _railway-verify.www; created it and the domain verified + routed within ~3 minutes. Thank you!


Status changed to Solved 0x5b62656e5d about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...