2 days ago
Hi Railway team,
My custom domain app.stillflying.app stays at CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP (verified: false). Railway reports the DNS record as PROPAGATED and public resolvers agree.
Attempt 1: stuck for several hours with correct DNS. I deleted and re-added the domain.
Attempt 2 (current): new CNAME target 64bmesfh.up.railway.app, updated at my DNS host, stuck for 1.5h+.
CNAME app -> 64bmesfh.up.railway.app, no proxy, TTL 600. No CAA records.
The service responds fine on its *.up.railway.app domain.
Plan: trial, one custom domain.
Could someone check why validation never completes, or retrigger certificate issuance?
(Drafted with help from an AI assistant; the facts above are from my own setup.)
1 Replies
2 days ago
The traffic CNAME is correct, but the domain is still missing its ownership verification record. Verification has to pass before a certificate can issue, and a public lookup of that TXT host currently returns nothing.
At your DNS host, add a TXT record with host _railway-verify.app and value railway-verify=e28910f7eb9e1c61852c357fce3a1a805ddd7732537821ac61c4d3710068e255. The token belongs to the current domain entry, so a record from your first attempt would not match it.
Once the record propagates, verification and certificate issuance continue on their own. You don't need to remove and re-add the domain, and doing that would generate a new CNAME target and a new token.
Status changed to Awaiting User Response Railway • 2 days ago