22 days ago
Custom domain www.caprockog.com on service caprock-site (project caprock-operating)
has been stuck in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for 7+ hours.
Your own API reports the DNS as correct and settled:
requiredValue = gkjtmp5t.up.railway.app
currentValue = gkjtmp5t.up.railway.app
status = DNS_RECORD_STATUS_PROPAGATED
The service has a successful deployment and serves fine on
caprock-site-production.up.railway.app. The custom domain serves your
CN=*.up.railway.app wildcard instead of a cert for the hostname, so browsers
fail with ERR_CERT_COMMON_NAME_INVALID.
Another custom domain on this same account works normally
(www.pluggingservices.com has a valid Let's Encrypt cert), so this is not an
account-level configuration problem.
Already tried: waited well past the 3600s TTL; called
customDomainUpdate(id, environmentId) to force revalidation (returned true, no
change); confirmed the domain is attached to the right service and environment.
Please manually trigger issuance, or tell me what is blocking validation.
1 Replies
22 days ago
The CNAME is propagated correctly, but the ownership-verification TXT record is missing. A second DNS record is required: a TXT record at _railway-verify.www with the value railway-verify=1a36655aca875cc1a7879ca9fbc2260750aa9f0a8cfffb5ac840546ecfe36f93. Add that at your DNS provider, and once it propagates, verification and certificate issuance will resume on their own.
Status changed to Awaiting User Response Railway • 22 days ago
15 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 • 15 days ago