22 days ago
Two custom domains on my web service are stuck at certificate status
VALIDATING_OWNERSHIP and the cert never issues, even though DNS is correct and
Railway confirms it sees the right CNAME.
Project: PitchIQ — 8147aa8e-c705-45be-b259-17919f56cf99
Service: PitchIQ OG (web) — 55dee29d-ede6-42fe-adb0-f92f92e14d61, env production
Affected domains (CNAME'd directly to the Railway targets, targetPort 3001):
- community.doctorstafford.com -> CNAME ozjnjzcx.up.railway.app
- chuhching.com -> its Railway target
Both stuck at VALIDATING_OWNERSHIP for hours. The API shows dnsRecords
currentValue == requiredValue, status PROPAGATED (Railway sees the correct
CNAME), yet certificateStatus never advances.
Verified: DNS correct on Google 8.8.8.8 + Cloudflare 1.1.1.1 (→ edge IPs
69.46.46.x); no CAA records; targetPort=3001 (matches the working pitchiq.live
domain); deleting + recreating community.doctorstafford.com left it stuck
identically. Domains with valid certs here (pitchiq.live, www.pitchiq.live) are
Cloudflare-fronted; the two stuck ones point straight at the Railway edge.
Please look into why ownership validation isn't completing for these
direct-edge custom domains. Thanks!
1 Replies
22 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 22 days ago
22 days ago
You need to add a TXT record at _railway-verify.community.doctorstafford.com. Railway uses TXT records to verify domain ownership. If you are using the API to add your custom domain, you can find the TXT record in verificationToken under status.