a month ago
Hi team,
I'm trying to add the apex domain tantisierrasclub.org (no www) as a custom domain on my service (project: sodiclub, service: sodiclub), but the TLS certificate fails to issue with this error:
Failed to issue TLS certificate — Let's Encrypt rate limit reached. Please wait before retrying. This error cannot be automatically retried.
DNS is already correctly configured and verified in Namecheap (not a missing-record issue):
- ALIAS record: @ → xseh9cb4.up.railway.app — verified
- TXT record: _railway-verify — verified
The www subdomain (www.tantisierrasclub.org) is already live and working fine on the same service — this error only affects the apex domain.
This started around the time of the October 21 security incident (QH8L8B3E), so I suspect it may be related to the platform-wide certificate reissuance mentioned in that incident. The incident is now marked as Resolved, but the error on my end persists and can't be retried automatically.
Could you please help clear the rate limit / manually retry certificate issuance for this domain?
Thanks, Danilo
4 Replies
a month ago
Ownership verification for the apex domain has passed and its record pointing at your service is in place, so your DNS is not the problem. The certificate failed because Let's Encrypt is rate-limiting that name after repeated failed issuance attempts, and waiting for that limit to clear is the only remedy, since a new attempt before then fails the same way.
Status changed to Awaiting User Response Railway • 27 days ago
Railway
Ownership verification for the apex domain has passed and its record pointing at your service is in place, so your DNS is not the problem. The certificate failed because Let's Encrypt is rate-limiting that name after repeated failed issuance attempts, and waiting for that limit to clear is the only remedy, since a new attempt before then fails the same way.
a month ago
Understood, thanks. Could you let me know roughly how long this rate limit typically takes to clear, or whether it's possible to manually force a retry on Railway's side once it does? I'd rather not keep attempting and risk extending the limit further.
Status changed to Awaiting Railway Response Railway • 27 days ago
a month ago
The certificate for the apex domain still shows the same rate-limit failure, and your ownership verification and DNS record still check out. Holding off on new attempts is the right call. Another attempt before the limit clears will fail the same way.
We can't give you a reliable clearing time. The limit is set and enforced by Let's Encrypt, so neither we nor you can lift it early.
Status changed to Awaiting User Response Railway • 27 days ago
a month ago
Same here since the 21 Oct incident: a brand-new custom domain failed its very first certificate attempt with “Let’s Encrypt rate limit reached … cannot be automatically retried.” Railway’s bot confirmed my DNS and ownership are fine and the only blocker is the Let’s Encrypt order. There’s no CAA, and no certificate was ever issued for the name. A domain in the same zone got its certificate on 16 Oct, before the incident. That looks like a platform-side problem with new certificate orders, not DNS. +1 for a Railway engineer to check whether issuance is affected platform-wide.
Status changed to Awaiting Railway Response Railway • 27 days ago
Status changed to Awaiting User Response Railway • 27 days ago
20 days 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 • 20 days ago