2 months ago
Project: lucky-victory · Service: bountiful-compassion · Environment: production
Domain: www.homescoutnz.co.nz → target 2dgfwp1v.up.railway.app
The dashboard shows the domain as verified (green tick, no error). DNS is correct and confirmed propagated on both Google (8.8.8.8) and Cloudflare (1.1.1.1) resolvers: CNAME www → 2dgfwp1v.up.railway.app, plus the _railway-verify.www TXT record. There are no CAA records on the domain or its parents, so Let's Encrypt is not being refused. No conflicting A/AAAA records.
Requests to https://www.homescoutnz.co.nz connect to the edge and then abort during the TLS handshake (~900ms). The underlying target https://2dgfwp1v.up.railway.app serves correctly over HTTPS. This points to the certificate never being issued or not propagating to the edge.
Context: the domain was removed and re-added roughly an hour ago, which reassigned the target from zeovpzkq.up.railway.app to 2dgfwp1v.up.railway.app. The edge may be holding stale state from that change. Could you force certificate re-issuance server-side? I'd rather not delete and re-add again, as that would change the CNAME target a second time.
1 Replies
2 months ago
Your custom domain www.homescoutnz.co.nz is now fully operational: the certificate is valid, DNS is propagated, and edge routes are installed. The TLS handshake issue you experienced has resolved, likely as the certificate finished propagating to the edge after the domain re-add.
Status changed to Awaiting User Response Railway • about 2 months ago
a month 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 • about 1 month ago