2 months ago
Custom domain: www.achadinhosdasho.com
Service: n4-checkout
Certificate stuck at CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for 12+ hours
(multiple recreations, multiple customDomainIssueCertificate calls).
Your GraphQL customDomain query dnsRecords[0].currentValue OSCILLATES between
3 stale values across requests
Suggests inconsistent DNS cache across your validation resolvers.
HTTP edge already accepts traffic for the hostname (301 to HTTPS works,
x-railway-67 header present) but HTTPS routing to service returns "Application
not found", appears to be gated on cert emission.
Please:
- Force-flush the stale entries in your DNS validation cache
- Trigger fresh Let's Encrypt issuance if rate-limited
3 Replies
2 months ago
The certificate cannot advance because the required TXT ownership-verification record is missing. Your CNAME is correct and propagated, but certificates will not issue until a TXT record is also present. At your DNS provider (GoDaddy, based on the nameservers), create a TXT record with host _railway-verify.www and the verification value shown in the Railway dashboard under your custom domain settings. Once that propagates, verification and certificate issuance should proceed automatically. Reply here after adding it and we can confirm propagation.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
Thank you for bringing this to my attention. I updated the TXT record now
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Your TXT record has propagated and the certificate is now valid. www.achadinhosdasho.com should be serving over HTTPS normally.
Status changed to Awaiting User Response Railway • about 2 months ago
a month 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 • about 2 months ago