13 days ago
Same defect as the solved thread "URGENT: Custom domain stuck in VALIDATING_OWNERSHIP despite correct DNS for 11+ hours" (events.karima.org.uk, solved by brody): the ownership-validation workflow exhausted its retries before DNS was correct and never re-ran after propagation.
Affected domains, both on the same service in my account (sequoiaqualitysolutions):
- www.sqstrendlab.com
- app.sqstrendlab.com
Both CNAMEs are propagated and match requiredValue per your API (DNS_RECORD_STATUS_PROPAGATED). Triggering customDomainIssueCertificate via the API returns true but status remains VALIDATING_OWNERSHIP, consistent with the karima case where only a server-side kick resolved it. No CAA records, DNSSEC off, registrar Namecheap.
Please re-trigger ownership validation server-side for both domains.
2 Replies
13 days ago
Both domains have their CNAME records propagated correctly, but neither has the required TXT ownership-verification record published in DNS. Custom domains need both a CNAME for routing and a TXT record for ownership verification. You can find the exact TXT record names and values for each domain on the domain settings page in your project. Add those TXT records at your registrar (Namecheap), and once they propagate, verification and certificate issuance will proceed automatically.
Status changed to Awaiting User Response Railway • 13 days ago
12 days ago
Make sure to add a TXT record at _railway-verify.<DOMAIN> where <DOMAIN> is the domain you’re trying to add. If you’re using the API, you can find the content for the record from the verificationToken property under status.
Status changed to Awaiting Railway Response Railway • 12 days ago
Status changed to Awaiting User Response Railway • 12 days ago
5 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 • 5 days ago