18 days ago
Our custom domain threads.insightlab.co.jp is still in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP with verified=false, approximately 18 hours after both required DNS records were added (around 2026-09-17 18:10 UTC). The domain entry was created on September 13, before DNS was configured. Latest Railway status checked at 2026-09-18 12:10 UTC remains unchanged.
Project: eba5c183-e525-4774-a51a-276c74705b86
Environment: 899f034c-1689-4fda-9578-cd73de829bbb
Service: bb8ae5ba-3e49-4040-aab2-8d4d972c1f04
Custom domain ID: 9741389b-76f9-40fd-83a9-9b5d45dae41b
Checks completed:
- CNAME threads.insightlab.co.jp points to m4jzmkzv.up.railway.app, DNS-only (not proxied).
-
- TXT _railway-verify.threads.insightlab.co.jp exactly matches the current token in the Railway dashboard and API. Please compare it internally; no credentials are included in this report.
-
- Both records matched on Cloudflare authoritative nameservers mira.ns.cloudflare.com and rudy.ns.cloudflare.com, and public resolvers 1.1.1.1, 8.8.8.8 and 9.9.9.9 at 02:41 UTC today.
-
- Railway reports DNS_RECORD_STATUS_PROPAGATED and syncStatus ACTIVE, but ownership remains unverified. At 02:41 UTC, certificateErrorMessage, certificateErrorType and certificateRetryable were all null.
-
- No restrictive CAA records were found at the custom hostname, zone apex or CNAME target. No DS record exists at the zone apex; DNS queries returned NOERROR.
-
- The default Railway URL is healthy (HTTP 200 at /api/health); the custom hostname fails TLS hostname validation.
-
- A prior certificate retry was rejected because the state was not FAILED. We have not repeated it, deleted/recreated the domain, or weakened TLS settings.
Could you inspect the ownership verification/reconciliation job and tell us whether any additional configuration is required? If appropriate, please re-trigger ownership validation and certificate provisioning for this existing domain without deleting it or interrupting the existing Railway URL. Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • 18 days ago
18 days ago
Your DNS records are correctly configured and the verification TXT matches the expected token. The ownership check retries for up to 72 hours from when the domain entry is created, and since the entry was created on September 13 with the records added around September 17, those retries had completed before the records were in place. We've started a certificate re-issuance for this domain, which may take a few minutes to complete.
Status changed to Awaiting User Response sam-a • 18 days ago
11 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 • 11 days ago