25 days ago
Hi Railway team,
I’m on the Hobby plan. The custom domain clientes.teamsodalab.com on project [nombre del proyecto], service [nombre del servicio], has been unable to get a TLS certificate for more than a day.
Error shown in the dashboard: “Failed to issue TLS certificate – Let’s Encrypt rate limit reached”.
DNS is correct and has propagated (checked on 8.8.8.8 and 1.1.1.1):
CNAME clientes.teamsodalab.com → 9j2nkfy4.up.railway.app
The _railway-verify TXT record you requested is in place.
Current behavior: the domain reaches my service (the app answers with HTTP 200), but the edge still serves the default certificate (CN=*.up.railway.app, issued by Let’s Encrypt YE2). Browsers reject it with a name mismatch.
What I’ve tried: I removed and re-added the custom domain once, which gave me the new CNAME target above. I haven’t retried since then, so I don’t add more attempts against the rate limit.
Could you check the certificate issuance for this domain on your side and retry it, or tell me when the rate limit will clear? If anything is missing in my DNS setup, please let me know.
Thanks!
3 Replies
25 days ago
We checked your custom domain. The CNAME is propagated and points at the correct target, and ownership verification has passed, so nothing is missing from your DNS setup.
The certificate failed because Let's Encrypt is rate-limiting new certificates for this name after repeated failed attempts. Waiting is the only fix, because any new attempt before the rate limit clears fails the same way. You were right not to retry, and removing and re-adding the domain again would also count as a new attempt.
Status changed to Awaiting User Response Railway • 25 days ago
Railway
We checked your custom domain. The CNAME is propagated and points at the correct target, and ownership verification has passed, so nothing is missing from your DNS setup. The certificate failed because Let's Encrypt is rate-limiting new certificates for this name after repeated failed attempts. Waiting is the only fix, because any new attempt before the rate limit clears fails the same way. You were right not to retry, and removing and re-adding the domain again would also count as a new attempt.
25 days ago
Thanks for confirming the DNS is fine. One question: the dashboard says this error "cannot be automatically retried". Once the rate limit clears, will Railway retry the certificate on its own, or does someone need to trigger it? Roughly how long does this rate limit usually last?
Status changed to Awaiting Railway Response Railway • 25 days ago
24 days ago
Apologies for the trouble, this related to an account issue today with our TLS certificate provider. We are back now, please click try again where the error arose in the UI. If this button doesn't regenerate it, please try removing the domain and adding again.
Status changed to Awaiting User Response Railway • 24 days ago
Status changed to Solved dizzydes90 • 24 days ago