a month ago
Project: wild-valley (22a1b623-eeba-4ca5-8bd8-9217bc9afbed), environment production, service "web". Pro plan.
Issue: custom domains www.wildvalleyevents.com and wildvalleyevents.com (apex) never get registered on Railway's edge. The service's Railway-provided domain https://web-production-bd8ff.up.railway.app works fine (200). Since Aug 23 (~15+ hours), both custom domains sit in status VALIDATING_OWNERSHIP and requests for those hostnames return 404 "Application not found" from the edge.
What I have verified:
- DNS: both records are CNAMEs in Cloudflare pointing at the requiredValue targets Railway gave me (www -> imu5j4yo.up.railway.app, apex -> kbds6bii.up.railway.app). Railway's own dnsRecords status reported PROPAGATED repeatedly.
-
- No CAA records on the zone, no DNSSEC (no DS record). Cloudflare proxy on (orange cloud), SSL mode Full.
-
- I deleted and recreated both custom domains 3 times (customDomainDelete + customDomainCreate), waiting ~2 hours each time; certificates stayed in VALIDATING_OWNERSHIP and the hostnames never routed.
-
- Reproduction independent of DNS: curl -H "Host: www.wildvalleyevents.com" https://web-production-bd8ff.up.railway.app/ returns 404 "Application not found", while the same request with the Railway domain as Host returns 200. So the edge does not know these hostnames at all.
-
- No incident on the status page during this window. (I do see another thread from today, "Custom domain CNAME verification target keeps changing", which may be related.)
Current custom domain IDs: www = 83304be1-1067-4d58-a8e2-a957c7f5e0ed, apex = 436ccfe6-298d-4b2a-9c60-ff8601fc913e.
Could you check why these hostnames are not being provisioned on the edge for this service? Happy to delete/recreate again if you need a fresh attempt on your side. Thanks!
2 Replies
a month ago
Both custom domains are missing their TXT ownership-verification records, which is why they stay in VALIDATING_OWNERSHIP and never register on the edge. The CNAME traffic records are correctly propagated, but Railway requires a second record for each domain: a TXT record at the verification hostname shown in each domain's settings (the _railway-verify.* name) containing the token value displayed there. Add those two TXT records in Cloudflare, wait for propagation, and the domains should verify and begin issuing certificates.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Resolved. Confirmed the cause was the missing _railway-verify TXT records (only the CNAMEs were in place). Added both TXT records in Cloudflare, ran customDomainIssueCertificate for each domain, and within ~2 minutes the edge registered both hostnames and certificates were issued. Thanks!
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved Railway • about 1 month ago