a month ago
Two custom domains have been stuck on CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for several days, despite DNS records showing as PROPAGATED.
Project: gracious-adventure (f87a3bf6-a475-4654-9ef2-29034db7b51b)
Environment: production (aa3a92c7-287a-457a-b688-238ebfcc5f3d)
Domain 1: app.ofek.com.ar
Service: ofek-app-frontend (7bb3a489-8fdf-4203-80af-5b978bbc8b96)
Custom domain ID: 3faf59e3-4f8b-49f5-9297-4f6b1cc79920
CNAME target: wmdlyg2s.up.railway.app
Domain 2: admin.ofek.com.ar
Service: ofek-admin-frontend (fce25483-909f-495d-962b-b1e1137f01e5)
Custom domain ID: fd673a7b-64dd-48af-a923-d67165a3a0b5
CNAME target: ovprngpf.up.railway.app
DNS is managed via Cloudflare (DNS only / proxy off), delegated from NIC Argentina. I already tried: deleting and re-adding both domains once, confirmed no CAA records blocking issuance, and confirmed Cloudflare proxy is off. Could you check what's blocking certificate issuance on your end?
1 Replies
a month ago
Both domains are unverified because neither has a TXT ownership-verification record in DNS. The CNAME records for traffic routing are propagated, but certificates will not issue until a TXT record is also present for each domain. For Domain 1, add a TXT record at the verification host shown in its settings (the _railway-verify subdomain), and do the same for Domain 2. The exact record names and values are visible in each service's Settings under Networking. Once those TXT records propagate, verification will complete and certificates will issue.
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 • 28 days ago