18 days ago
Project a22896d8-29fe-4b9d-b782-36fe0631c263, service web (b43e9459), domain www.onlineshoppingisnotfun.com. The domain has been deleted/re-added 4× ; each time a new CNAME target was minted and our DNS (GoDaddy, TTL 3600) was updated — currently 8tvrr2yg.up.railway.app, confirmed identical on both authoritative nameservers. Your dashboard/API report the DNS record as PROPAGATED with currentValue == requiredValue, but certificateStatus never leaves CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP and the edge still serves the *.up.railway.app wildcard. No CAA or DNSSEC on the domain. Can you kick or inspect the issuance job?
1 Replies
18 days ago
Your CNAME is correct and propagated, but the TXT ownership-verification record is missing. Certificates will not issue until both are present. In GoDaddy, add a TXT record with the host and value shown in your Railway dashboard under the domain's DNS settings (the TXT record host will be _railway-verify.www). Once that propagates, the certificate pipeline will advance automatically.
Status changed to Awaiting User Response Railway • 18 days ago
11 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 11 days ago