a month ago
Hi,
I’m having an issue with the TLS certificate for the apex domain granjacanals.cat.
https://www.granjacanals.cat is working correctly, but https://granjacanals.cat still fails because Railway is presenting a *.up.railway.app certificate instead of a certificate valid for granjacanals.cat.
The apex DNS is configured using an ANAME record pointing to the target provided by Railway, and the _railway-verify TXT record is also configured. Railway previously recognized the ownership verification.
DNS routing appears to be working because requests to granjacanals.cat are already reaching the Railway edge; the remaining issue seems to be certificate issuance.
The DNS changes were completed on August 22, 2026, and the issue is still present on August 23.
Could someone from Railway check whether the certificate issuance/validation workflow for this custom domain is stuck and, if necessary, retry the certificate issuance?
I can provide project/service/domain IDs privately if required.
Thanks.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Good news, this one's already sorted. Your apex domain now has its own valid Let's Encrypt certificate, issued this morning (23 August), and it's live on our edge. A check from here returns a valid certificate for the apex with no SSL errors, so the *.up.railway.app fallback is no longer being served.
Your DNS and ownership verification were both fine. The certificate finished issuing and rolling out to the edge shortly after you wrote in, and that last step can lag a little behind verification, which is why you were still seeing the fallback certificate at the time.
If your browser still shows the old certificate, that's local caching. A hard reload, an incognito window, or a check from another network will confirm it.
Status changed to Awaiting User Response dizzydes90 • about 1 month ago
Status changed to Solved dizzydes90 • about 1 month ago