21 days ago
Project: 260e46f9-aa65-4d9f-82b2-79b0d2e49690
Service: secure-wholeness (91f4131e-86b5-4352-884a-d34557b94eca)
Environment: production (3ec6748f-2fa8-4f66-9f7d-583b69550c04)
Domain ID: 5d026ec3-88bd-43e7-ac1d-8ced255386b2
Domain: www.sistobuy.com
This custom domain was added over an hour ago. DNS is confirmed
correctly configured (CNAME www -> 6vkxn1mo.up.railway.app),
independently verified via nslookup against both 8.8.8.8 and 1.1.1.1.
However, the edge still serves the wildcard *.up.railway.app
certificate (RemoteCertificateNameMismatch) instead of a dedicated
certificate for sistobuy.com, and the site returns Railway's
"Not Found - domain has not provisioned" page.
Could you please manually check and complete certificate
provisioning for this domain?
1 Replies
21 days ago
Your CNAME record is correctly propagated, but the TXT ownership-verification record is missing. Custom domains require both a CNAME for routing and a TXT record for ownership verification - without the TXT record, the domain stays in "validating ownership" and returns a 404. In your service's settings under the custom domain entry, you'll see the required TXT record (host _railway-verify.www with the verification value shown in the dashboard) - add that at your registrar alongside the existing CNAME, and the certificate will issue automatically once it propagates. You can reply here after adding it so we can confirm it picked up.
Status changed to Awaiting User Response Railway • 21 days ago
14 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 • 14 days ago