4 hours ago
Project: d341458f-afef-437b-97f1-8de25a38ceb7
Environment: production (68819d3f-0f1c-4e2e-bb28-fe07807e51dd)
Service: web (0589e05b-5883-4f34-90db-aa45f6a63b8a)
Domain id: 1d95132c-8188-4d3f-842e-ec9f19bc41c9
The custom domain www.subphaisal.com was added on 9 Sep 2026 (~06:00 UTC) and its certificate has been stuck at CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP ever since, with errorMessage null. Requests to https://www.subphaisal.com return a hostname-mismatch TLS error (the default certificate is served), so the certificate has never been issued.
Everything on our side checks out. The CNAME www -> uvlaz4ai.up.railway.app is correct and Railway reports DNS_RECORD_STATUS_PROPAGATED (we independently verified propagation via public resolvers). subphaisal.com has no CAA records and DNSSEC is not enabled. DNS is hosted at Namecheap with no proxy (no Cloudflare) in front. The app listens on port 8080 (confirmed in deploy logs) and the domain's targetPort is 8080. The apex domain subphaisal.com on the same service has a valid certificate and serves traffic normally.
Could you retry or force certificate issuance for this domain server-side? We would prefer not to delete and re-add the domain, since that would change the CNAME target and require another DNS change on our side. Happy to provide anything else you need.
1 Replies
4 hours ago
Your CNAME is correctly propagated, but the domain is missing its TXT ownership-verification record. Each subdomain needs its own verification record, separate from the apex. Open the domain's settings in the Railway dashboard under "Show DNS records" to see the required TXT host and value, then add that record at your DNS provider. Once it propagates, verification and certificate issuance will resume automatically.
Status changed to Awaiting User Response Railway • about 4 hours ago