a month ago
Two custom domains on service reachease-app (project 776a5a4f-de1d-404d-b595-8a932803bc90, env production, Hobby plan) have been stuck at CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for hours:
www.reachease.io → CNAME ya6wnplu.up.railway.app — your API reports DNS_RECORD_STATUS_PROPAGATED and currentValue matches requiredValue exactly, DNS-only (no proxy), no CAA records on the zone.
app.reachease.io (domain id 7c19d24e-cfa3-4166-ab3c-85809441cc12) — same symptom before we rolled its DNS back to our old host to end user impact.
railway domain certificate retry refuses because the status is VALIDATING rather than failed. Deleting and re-adding the domain starts a fresh cycle that stalls identically. Could you kick the certificate workflow for www.reachease.io? Once it issues we'll re-point app.
1 Replies
a month ago
The certificate is stuck because the TXT ownership-verification record has not been added yet for either domain. The CNAME traffic record is propagated correctly, but certificates also require a separate TXT verification record to prove domain ownership before they can issue. You can find the exact TXT record name and value in your service's Settings under Networking, next to each custom domain entry. Once you add that TXT record at your DNS provider and it propagates, verification will pass and the certificate will issue automatically. For the second domain, you will also need to re-point its CNAME to the target shown in the dashboard (it currently resolves to your old host) and add the corresponding TXT record.
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 • about 1 month ago