a month ago
Project: Ecosistema-Digital-FAME (cf0d005f-423a-469f-9740-c500b22b1a8f), workspace edgargarcia-bit's Projects
Environment: production (94a7215d-b3d4-44c1-895e-c39350c39e1a)
Service: portal-fame (ad17176a-5145-4f8c-bfef-3ca898de83df)
Custom domain: backoffice.famesc.com (domain id 05d178cf-77c3-4312-9bf2-e477cb7df879)
PROBLEM: backoffice.famesc.com returns 404 with x-railway-fallback: true (server railway-hikari) on every request. The edge has no route for this hostname even though on your side the domain is fully verified: CNAME currentValue == requiredValue == wk3ycjfh.up.railway.app, status DNS_RECORD_STATUS_PROPAGATED; certificateStatus CERTIFICATE_STATUS_TYPE_VALID; only one required record (the CNAME, purpose TRAFFIC_ROUTE), no TXT requested.
The service is healthy (portal-fame-production.up.railway.app returns 200). Other custom domains in the same project route fine: www.famesc.com 200 and famesc.com 415, both on service sitio-fame. Only backoffice.famesc.com to portal-fame falls back. This isolates it to a stuck edge binding for this single domain record.
ALREADY TRIED (no effect): customDomainUpdate targetPort 8080 to null (auto); full redeploy of portal-fame (SUCCESS, waited 2 min); customDomainIssueCertificate (cert VALID); confirmed no duplicate/ghost domain record on any other service; forcing Host: backoffice.famesc.com against the edge still returns x-railway-fallback: true.
CONSTRAINT: We do NOT control the DNS zone for famesc.com and cannot request changes from the current DNS operator. The usual delete-and-re-add fix reassigns the CNAME target to a new hash.up.railway.app, which we cannot publish. We need backoffice.famesc.com re-bound to portal-fame at the edge WITHOUT changing the required CNAME target (must stay wk3ycjfh.up.railway.app).
ASK: Please force a server-side re-provision / rebind of backoffice.famesc.com to portal-fame in production, keeping the current CNAME target wk3ycjfh.up.railway.app. If a rebind unavoidably changes the target, tell us the exact new value; ideally keep wk3ycjfh so no DNS change is needed. Thank you.
4 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
Your TXT record is malformed. It should start with railway-verify=. Make sure you're using whatever Railway provided and not modifying the content.
If you're using the API, you can get the content for the TXT from the verificationToken property under status.
0x5b62656e5d
Your TXT record is malformed. It should start with `railway-verify=`. Make sure you're using whatever Railway provided and not modifying the content. If you're using the API, you can get the content for the TXT from the `verificationToken` property under `status`.
a month ago
the original project description explicitly states that no TXT record was requested, only the CNAME record.
h701h
the original project description explicitly states that no TXT record was requested, only the CNAME record.
a month ago
A TXT record is always needed, and one was provided; OP is incorrect.
brody
A TXT record is always needed, and one was provided; OP is incorrect.
a month ago
Thanks for the clarification. I'm still learning the platform deeply.
