a month ago
Custom domain www.restaurantembrasa.pt on service site-m-brasa has been stuck in VALIDATING_OWNERSHIP for 24+ hours and is not being routed - requests get a Railway edge fallback 404 (x-railway-fallback: true), while the app itself works fine on its default *.up.railway.app domain.
Project: carta-digital-staging / Environment: production / Service: site-m-brasa (092d7660-4c59-40d8-9e65-cab8f3a18724) / Custom domain ID: 79114fe4-44d6-4b14-a47e-1dbde053931c
DNS confirmed correct and fully propagated, checked via public DoH resolver, not just locally: www.restaurantembrasa.pt CNAME ox41j5c1.up.railway.app - matches dnsRecords.requiredValue exactly, status already shows DNS_RECORD_STATUS_PROPAGATED.
What I've tried: called customDomainIssueCertificate 3 times over 24h with no change; deleted and recreated the custom domain once (got a new required CNAME target, updated DNS to match) - avoiding doing this again after reading similar threads here about Let's Encrypt duplicate-certificate rate limits; confirmed no CAA record is blocking issuance; curl -v reaches your edge (x-railway-edge visible) but returns 404 with x-railway-fallback: true.
I found several very similar recent threads here (e.g. "Custom domain stuck on VALIDATING_OWNERSHIP despite correct DNS", 8 days ago) where a Railway employee manually re-triggered the certificate validation workflow on your side to fix it. Could someone do the same for this domain?
Thanks!
1 Replies
a month ago
The CNAME is correct and propagated, but the TXT verification record on the verification host contains a stale token from the previous domain entry (before you deleted and recreated it). The current value does not match what the new entry expects, so ownership validation cannot complete. Open your service's Settings, Networking section, expand the DNS records for that custom domain, and copy the current verification TXT value shown there, then update the TXT record at your registrar to match it exactly. Once propagated, verification and certificate issuance should proceed automatically.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 26 days ago