25 days ago
My custom domain golf.dallascsifoundation.org won't provision its TLS certificate.
Project: 0d2e38ee-e016-49b1-a49a-622eb13bc434
Service: topgolf-tournament
- DNS is correct: it's a DNS-only (not proxied) CNAME → ln75vr1w.up.railway.app → 69.46.46.116. No CAA records on the zone.
- The certificate first sat in ISSUING for ~3 hours. I deleted and re-added the domain to restart it; it's now stuck in VALIDATING_OWNERSHIP and not progressing.
- The .up.railway.app domain and the service itself serve fine over HTTPS.
Could you please force certificate issuance, or investigate why ownership validation isn't completing? Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • 25 days ago
25 days ago
The CNAME traffic record is propagated correctly, but the TXT ownership-verification record is missing entirely, which is why the certificate is stuck validating. Add a TXT record at host _railway-verify.golf (your DNS provider appends the zone automatically) with the value railway-verify=41f5c8bb0b29cc3003ddbb2fa266ead2c6c6fb3ac4757fd5f8bfcf65e201f417. Verification and certificate issuance will resume automatically once that record propagates.
Status changed to Awaiting User Response Railway • 25 days ago
18 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 • 18 days ago