21 days ago
Project: mindful-appreciation (0b121c58-1291-4f1b-a576-c563bb9a6810)
Service: SMARTPLAY-PLAYER (20dec6b0-ea4e-4ce8-9bd6-4b9a106d18da)
Environment: production
4 custom domains were added ~24 hours ago after migrating DNS from NeuBox to Cloudflare (DNS-only mode, proxy disabled):
- smartplayplayer.com -> CNAME q7v0ggef.up.railway.app (flattened at apex via Cloudflare)
-
- www.smartplayplayer.com -> CNAME w1aciou1.up.railway.app
-
- smartplayplayer.com.mx -> CNAME aaupus6p.up.railway.app (flattened at apex via Cloudflare)
-
- www.smartplayplayer.com.mx -> CNAME 54e3sck3.up.railway.app
All 4 domains show DNS_RECORD_STATUS_PROPAGATED via the domain-status API, correctly matching the required CNAME targets, and have shown this status unchanged for over 12 hours. However, all 4 remain stuck at certificate.status = CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP with verified: false and errorMessage: null.
No CAA records exist on either domain (confirmed via Cloudflare DNS records list). Cloudflare proxy is off (grey cloud / DNS-only) for all 4 records, so Let's Encrypt's HTTP-01 challenge should reach Railway's origin directly. Could someone check on Railway's side why ownership validation isn't progressing despite correct, fully propagated DNS for this long?
Happy to provide any additional info needed.
1 Replies
20 days ago
Your CNAME records are in place, but certificates also require a TXT ownership-verification record for each domain, and those are what's missing. In Cloudflare, add a TXT record for each: for the two apex domains use host _railway-verify, and for the two www subdomains use host _railway-verify.www. Set each record's value to the token displayed next to that domain in your service's Settings, Networking section (formatted as railway-verify= followed by a long hex string). Verification and certificate issuance resume automatically once the records propagate.
Status changed to Awaiting User Response Railway • 20 days ago
13 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 13 days ago