My custom domain has been stuck in "Validating domain ownership" for 30+ minutes
morresmx
HOBBYOP
a month ago
- DNS is clean and correct, confirmed directly via authoritative nameservers (not just public resolvers): single CNAME record pointing to the Railway-provided target, single TXT _railway-verify record with the exact expected value, no duplicate or conflicting records.
- Earlier in the process I briefly had a duplicate CNAME record (an old value left over from a previous attempt) pointing at the same hostname — this was found and removed, but the domain may have gotten stuck in a bad internal state as a result.
- I deleted and recreated the custom domain once while troubleshooting — no change, same stuck state, new CNAME target assigned but still stuck at the same step.
- The "Certificate retry" option isn't available: it says retry is only available after certificate issuance fails, and current status is still VALIDATING_OWNERSHIP.
- Found a similar resolved thread from a few days ago with the exact same symptom (domain stuck in VALIDATING_OWNERSHIP after a duplicate-CNAME cleanup) — in that case, a Railway employee had to manually trigger a certificate re-issue on the backend to unstick it.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
sam-a
EMPLOYEE
a month ago
Your DNS is correctly configured and domain ownership has already been verified, but the certificate pipeline stalled before advancing past the validation step. We've started a certificate re-issue for the domain, which should complete within a few minutes.
Status changed to Awaiting User Response sam-a • about 1 month ago
Status changed to Solved morresmx • about 1 month ago