a month ago
Project: matterica-copilot, service web, production environment.
Domains: matterica.ru (apex, via Cloudflare CNAME-flattening) and www.matterica.ru (plain CNAME).
Both have been in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for over 24 hours. DNS is correct and shows PROPAGATED in the dashboard — the CNAME targets resolve to your edge. Nameservers are on Cloudflare, proxy is disabled (DNS only), no CAA records, no DNSSEC.
Diagnosis: http://matterica.ru/.well-known/acme-challenge/ returns 404 from your edge, so the HTTP-01 challenge can never complete — the domain won't route until the cert is issued, but the cert won't issue until the challenge passes. I already deleted and re-created both domains once; it didn't help.
Could you manually re-trigger certificate provisioning for these two domains? Thanks.
1 Replies
Status changed to Awaiting Railway Response Railway • 27 days ago
a month ago
Both domains are missing the required TXT ownership-verification records, which is why certificates are stuck on validating. Your CNAME records are correct and propagated, but Railway requires a TXT record per domain before it verifies ownership and issues a certificate, and without it requests return 404. You can find the exact TXT record names and values for each domain in your service's Settings tab under Public Networking, next to each custom domain. In Cloudflare, create those TXT records with proxy disabled (DNS only). Once they propagate, verification and certificate issuance should complete automatically. You can also retry cert issuance via the CLI with railway domain certificate retry <domain> after the TXT records are in place. Reply here once they are set and we can re-check.
Status changed to Awaiting User Response mykal • 27 days ago
20 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 • 20 days ago