a month ago
A custom domain won't get its SSL cert on my Hobby project.
Project: hopeful-essence · Service: show · Project ID: a5c43ebb-1d9e-4e21-aed1-5c7fd721c192
Domain: www.pinocchio.live → target rrsw5h55.up.railway.app
DNS is correct — my Porkbun CNAME points to the exact target, and Railway's own domain status shows the DNS record as PROPAGATED / matching.
The cert has been stuck at "Waiting for DNS update" / VALIDATING_OWNERSHIP for 20+ minutes (24h+ on a previous target before I re-added it).
I already removed and re-added the domain fresh — DNS matches again, but the cert still won't issue (still serving the *.up.railway.app wildcard cert, so HTTPS to my domain fails).
Could someone force-reissue the cert or check why ownership validation isn't completing? Thanks!
1 Replies
a month ago
Your CNAME is correct and propagated, but the TXT ownership-verification record is missing. Custom domains require both a CNAME for traffic routing and a TXT record for ownership verification, and the certificate will not issue until both are in place. In your Porkbun DNS, add a TXT record with the host _railway-verify.www and the value shown in your domain's settings in the Railway dashboard, then allow a few minutes for propagation. Once Railway verifies ownership the certificate should issue automatically.
Status changed to Awaiting User Response Railway • about 1 month 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