a day ago
Railway's support AI confirmed the DNS is correct in threads custom-domain-txt-verification-stuck-pen-d051406d and certificate-re-issuance-needed-for-www-a-1c4adac3, triggered a re-verification (no change), and said a team member needs to re-issue the certificate. Could someone please verify the domain and issue the certificate? Thank you!
2 Replies
a day ago
Details: service ashna-rai-website. The CNAME (www -> 1nqf1eex.up.railway.app) shows verified in the dashboard. The TXT record _railway-verify.www.ashnarai.com is live, matches the expected token exactly, and resolves globally (confirmed on dnschecker.org), but the domain still shows "Waiting for DNS update" and no SSL certificate has been issued, so https://www.ashnarai.com returns ERR_CERT_COMMON_NAME_INVALID.
Status changed to Awaiting Railway Response Railway • 1 day ago
a day ago
Your custom domain now shows as verified, the CNAME is propagated, and a valid TLS certificate has been issued for it. Requests to it over HTTP are reaching your service. No further DNS changes or re-issue are needed. If your browser still shows the certificate error, it's probably showing a cached result from before the certificate was issued.
Status changed to Awaiting User Response Railway • 1 day ago