10 days ago
Hello,
My custom domain certificate has been stuck on VALIDATING_OWNERSHIP for several hours and is never issued, so HTTPS fails.
Project: vivacious-cooperation
Service: novasetters
Domains: novasetters.com and www.novasetters.com
DNS is configured correctly:
novasetters.com ALIAS -> f4umhwwl.up.railway.app
www.novasetters.com CNAME -> 24voel56.up.railway.app
Railway reports the www record as PROPAGATED. There are no CAA records blocking issuance and no DNSSEC. http://novasetters.com responds with a 301 to HTTPS, but HTTPS fails with a wrong-principal error because the certificate was never issued.
I also tried deleting and re-adding the root domain, which changed the target, and I updated the DNS record accordingly.
This looks identical to the thread about launcherry.me, where Chandrika said the certificate issuance process had stopped after verification finished and restarted it manually. Could you please restart certificate issuance for my domains as well?
Thank you.
1 Replies
10 days ago
Neither domain has passed ownership verification yet. We can't find a verification TXT record for either one, and the certificate can't be issued until those records exist. Verification only succeeds once both the CNAME and the TXT record are in place.
At your DNS provider, add a TXT record with host _railway-verify and value railway-verify=fb83b861deeb53cbaa434be8f1100360e249df443aed841889464abcf33cb290 for the root domain.
For www, add a TXT record with host _railway-verify.www and value railway-verify=09e7c3654ce3a8e2aec84682d0515b504ed4f5208e0c1466d4e9e42e8c1a8058.
Because you deleted and re-added the root domain, it has a new verification token, so any TXT value you copied before that no longer applies. Once the records propagate, verification and certificate issuance continue automatically.
Status changed to Awaiting User Response Railway • 10 days ago
Status changed to Solved echohack • 10 days ago