2 months ago
Subject: Custom domain TLS certificate stuck "Validating" for hours (correct DNS)
Hi Railway team — a custom domain on my project has been stuck at certificate validation for 2.5+ hours and won't issue a TLS cert, despite correct DNS confirmed by Railway's own dashboard.
Project: sincere-nurturing (a48c5b11-4e45-48d7-8ee2-19870876dfa9)
Service: web
Custom domain: www.vegusomr.com → required CNAME target q4nveeqh.up.railway.app
The CNAME is correct (DNS-only on Cloudflare) and resolves. Railway's dashboard shows the record Propagated with current value matching required exactly.
Certificate status has been "Validating ownership" for 2.5+ hours with no progress. Plan: Hobby.
I've verified DNS resolves, no CAA/DNSSEC blocking, re-added the domain, and there's no active Railway incident.
This is a new Railway account — if there's an anti-abuse hold or manual review gating my first custom-domain cert, could you please clear it or tell me what's needed? Thanks!
Pinned Solution
2 months ago
You need to add a TXT record at _railway-verify.www.vegusomr.com. If you're using the API, you can get the content for it from the verificationToken property under status.
1 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 2 months ago
2 months ago
You need to add a TXT record at _railway-verify.www.vegusomr.com. If you're using the API, you can get the content for it from the verificationToken property under status.
Status changed to Solved 0x5b62656e5d • 2 months ago