21 days ago
Custom domains are stuck in VALIDATING_OWNERSHIP even though DNS is fully propagated and matches Railway exactly.
Project: desirable-achievement
Environment: production
Service: okey-premium-prod
Domain 1:
duzokey.com.tr
Domain ID: 203dc7d1-7f83-4b87-9614-b090d5e10172
Domain 2:
Domain ID: dfd82f69-ae74-42c6-9309-4ba4dabb9239
Railway CLI reports for both:
Sync status: ACTIVE
Verified: no
Certificate status: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP
The required CNAME and TXT records are publicly resolvable and match Railway exactly.
Authoritative nameservers:
chase.ns.cloudflare.com
itzel.ns.cloudflare.com
Cloudflare proxy is OFF / DNS-only during validation.
Public DNS checks confirm:
- root TXT is present
- www TXT is present
- www CNAME resolves to the Railway target
I also tried:
railway domain certificate retry
but Railway returns:
"Certificate retry is only available after certificate issuance fails. Current status: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP."
Could you please manually re-trigger ownership validation / certificate issuance for both domains, or refresh the custom-domain verification workflow without deleting/recreating the domains?
The Railway-provided production domain is healthy.
1 Replies
Status changed to Awaiting Railway Response Railway • 21 days ago
21 days ago
Your DNS records are in place for both domains, with the verification TXT values matching the expected tokens and HTTP challenge requests reaching our edge. The ownership validation workflow expired before your DNS had propagated, so verification never completed. A certificate re-issuance has been started for both domains and should finish within a few minutes.
Status changed to Awaiting User Response brody • 21 days ago
13 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 • 13 days ago