a month ago
Custom domain TLS certificate stuck in VALIDATING_OWNERSHIP for ~2 hours.
Project: e01a3e82, service: gvc-portal.
Domain: api.gvcbus.com, domain id 9ba60cc6-fbfb-4ad2-a4ad-5befc8804568 (created 17:33Z today; a previous object d5696100 was stuck the same way from 16:23Z before we removed/re-added).
Railway reports the CNAME as PROPAGATED (target e7l0uq3t.up.railway.app, verified at the authoritative nameservers). No CAA record, DNSSEC off, no conflicting A/AAAA/TXT records, target port set to 8080. No error message is exposed in the API. Please kick or investigate the certificate issuance.
1 Replies
a month ago
The CNAME for traffic routing is propagated, but the required TXT record for domain ownership verification has not been created yet. Without it, the certificate stays in VALIDATING_OWNERSHIP. In your service's networking settings, expand the DNS records for this domain to find the TXT verification record details, then create that TXT record at your registrar. Verification and certificate issuance proceed automatically once the record propagates.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved asotorod • about 1 month ago