2 hours ago
on project marinegpt-intelligence
(b3ef0b7b-ed88-49e5-9a6b-94e929ad5283) has been stuck at
certificateStatus: VALIDATING_OWNERSHIP for several hours.
-
DNS: DNS_RECORD_STATUS_PROPAGATED, confirmed globally via Google DoH
-
CAA on marinegpt.in explicitly authorizes letsencrypt.org
-
Zero certs for intel.marinegpt.in in CT logs (certspotter) — issuance
appears to never even attempt, not rate-limited
-
api.marinegpt.in on a different (10-month-old) project, same DNS zone,
same CAA, works fine — 3 certs issued successfully over time
-
Tried: customDomainIssueCertificate mutation, full delete + recreate
(reassigned CNAME target ekadtepe→5viefr5n, DNS updated to match),
explicit targetPort:3000 — none unstuck it
Suspect this may be a new-project verification gate that isn't clearing.
Can you check the cert-issuance queue for this domain directly?
1 Replies
2 hours ago
The CNAME traffic-route record is propagated correctly, but the TXT verification record is missing entirely. Certificates cannot issue until Railway verifies domain ownership, and that requires a TXT record at the verification host shown in your service's Settings under Networking (the _railway-verify subdomain) with the token value displayed there. Add that TXT record at your DNS provider, and once it propagates the verification and certificate issuance will proceed.
Status changed to Awaiting User Response Railway • about 2 hours ago