18 days ago
Hi Railway team - the TLS certificate for our custom domain www.autosharenetwork.com has not been issued after more than a day. Browsers show NET::ERR_CERT_COMMON_NAME_INVALID, and the certificate served for the domain is the *.up.railway.app wildcard instead of one for our domain. DNS is set as instructed: www is a CNAME to q3m4u1ds.up.railway.app (re-issued target after a domain re-add; it previously pointed to prbpfbvh.up.railway.app), the root A record was removed, root forwarding points to https://www.autosharenetwork.com, and our Zoho mail MX/TXT records are untouched. The app itself is healthy at its Railway address. Can you check why the custom-domain certificate is stuck and issue it? Thank you.
1 Reply
18 days ago
Your CNAME is correct and resolving to the new target, but the ownership verification TXT record is missing, and the certificate cannot issue until it is in place.
At your DNS provider, add a TXT record with host _railway-verify.www and the value railway-verify=d0c24b4440294f0b062278c6c37d193bbd161d967f9c14cca5b28066f5c53fbb. Re-adding the domain generated this new token, so any TXT record created for the earlier domain no longer matches. Verification and certificate issuance continue automatically once the record propagates.
Status changed to Awaiting User Response Railway • 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