a month ago
Project: bluewater-web (787a74ab-62a8-4c69-a6c1-81666dfdf1ba)
Environment: production (846e3a25-433f-412e-86b5-867ffcbb542e)
Service: bluewater-web (f038791f-32a7-4274-a15e-d89904e96f1a)
Custom domain: www.skytidepoolsandspas.com (current entry target: 9zs8xjec.up.railway.app)
Symptom: HTTPS requests to the custom domain return
404 {"status":"error","code":404,"message":"Application not found"}
with x-railway-fallback: true, edge PoP iah1.
Sample request ID: Qe8ffrghTAqBjTMmGbGh5g (2026-07-14 21:10 UTC).
Reproduced across THREE fresh customDomain entries today (targets
s9rrqa4e → zxqivz1d → 9zs8xjec), including a delete + 15-minute cool-down
- re-add cycle. Every time:
-
dnsRecords: DNS_RECORD_STATUS_PROPAGATED, currentValue == requiredValue
(also confirmed at GoDaddy authoritative NS, 8.8.8.8, 1.1.1.1)
-
certificateStatus sticks at VALIDATING_OWNERSHIP until a manual
customDomainIssueCertificate mutation, after which it goes VALID and the
correct cert serves on the wire — but the edge STILL never routes the
hostname
-
The service serves perfectly on bluewater-web-production.up.railway.app
Also tried: explicit targetPort (8080), multiple redeploys while all
checks were green. This looks like the edge routing table at iah1 never
picks up the hostname mapping despite full verification. Please inspect/
rebuild edge routing for www.skytidepoolsandspas.com.
Pinned Solution
a month ago
You need to add a TXT record for _railway-verify.www.skytidepoolsandspas.com. If you are using the API to add your custom domain, you can find it in verificationToken under status.
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 need to add a TXT record for _railway-verify.www.skytidepoolsandspas.com. If you are using the API to add your custom domain, you can find it in verificationToken under status.
darseen
You need to add a TXT record for `_railway-verify.www.skytidepoolsandspas.com`. If you are using the API to add your custom domain, you can find it in `verificationToken` under `status`.
a month ago
Certificate status already goes valid after a manual mutation. You should focus on edge routing issue at iah1 point of presence, as edge server doesn't pick hostname mapping properly.
- Inspect and rebuild edge routing for www.skytidepoolsandspas.com domain at iah1 point of presence
a month ago
That was it. Added the TXT record (_railway-verify.www with the
verificationToken value from the API) and within five minutes the domain
verified and the site is live. Huge thanks darseen, accepting your solution.
And h701h, appreciate the sharp analysis too. The symptom really did look
like an edge routing failure until the verification field surfaced. Smart
people in this community.
One piece of feedback for the Railway team, offered with love because I
genuinely like this platform and it's why I host everything here: the
dashboard's "Show DNS records" only displayed the CNAME, and the API's
dnsRecords array doesn't include the TXT requirement either. It only lives
in status.verificationToken, which nothing in the UI surfaces. Meanwhile
the cert sits at VALIDATING_OWNERSHIP and the edge returns a 404 with no
hint that a DNS record is missing. If the dashboard listed the TXT next to
the CNAME, this whole thing is a five minute setup.
All good now. Site is live, cert is clean, and I'm a happy customer.
Thanks all.
Status changed to Solved 0x5b62656e5d • 28 days ago