a month ago
Project: kind-curiosity (90139c56-5ddf-4407-8575-313d464449e1)
Environment: eod-staging / Service: @workspace/api-server
Custom domain: eod.incrementalgains.io (id bee802d1-b236-41fe-8195-68fb6e4b0076)
The API reports the only required DNS record (CNAME eod → dmsiuvbn.up.railway.app, DNS-only/unproxied) as DNS_RECORD_STATUS_PROPAGATED, yet certificateStatus has been stuck at CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for over 24 hours. The edge still serves the *.up.railway.app wildcard cert for this hostname.
Evidence it's stuck server-side: (1) HTTP :80 on the hostname reaches your edge and 301s correctly, so HTTP-01 validation would succeed; (2) no CAA records or stale _acme-challenge records exist on the zone; (3) CT logs (crt.sh) show ZERO issuance attempts ever reached Let's Encrypt for this hostname; (4) the customDomainIssueCertificate mutation returns true but the status never changes. Note the domain was deleted/re-added twice during earlier debugging. Could you reset/retry certificate issuance for this domain?
1 Replies
a month ago
Your CNAME record is propagated correctly, but the domain is missing its TXT ownership-verification record, which is why the certificate is stuck at VALIDATING_OWNERSHIP. Custom domains require both a CNAME for traffic routing and a TXT record for ownership verification. You can find the exact TXT record name and value to publish in the domain's settings under your service's Networking section. Once that record propagates, verification and certificate issuance will resume automatically.
Status changed to Awaiting User Response Railway • 29 days ago
22 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 • 22 days ago