25 days ago
Hi all,
One of our custom domains can't get a TLS certificate. The dashboard shows:
"Failed to issue TLS certificate. Let's Encrypt rate limit reached. Please wait before retrying. This error cannot be automatically retried."
There is no "try again" button for this domain, so the fix suggested in https://station.railway.com/questions/tls-certificate-stuck-on-let-s-encrypt-ce60c54f doesn't apply. Retries through the API are refused with the same message.
What happened:
- At first the CNAME pointed at an outdated Railway target, so a number of issuance attempts failed validation.
- On 26 Oct around 16:45 UTC the CNAME was corrected. Railway shows it as current and propagated since then.
- The same evening Railway had the "TLS certificates not generating" incident. Since that was fixed, our domain is still stuck, with the last retry refused on 27 Oct around 07:30 UTC.
Questions for the team:
- Is this a real Let's Encrypt limit on our hostname (if so, which one and when does it reset), or a leftover state from the 26 Oct incident?
- Can you reissue the certificate or clear the non-retryable state?
We'd rather not delete and re-add the domain, because that gives a new CNAME target and our client would have to change their DNS again.
Happy to share the project and domain details in a private message.
Thanks!
1 Reply
25 days ago
The domain that's stuck is failing on a rate limit that Let's Encrypt set on that hostname. It isn't leftover state from the 26 Oct incident. The DNS record has been correct and propagated since your change, and the certificate error recorded for it is specifically a Let's Encrypt rate limit. That fits the run of failed validations while the CNAME still pointed at the old target.
For this error the only fix is to wait until Let's Encrypt's window clears. A reissue before then, whether from us or through the API, would fail the same way. We can't tell you the exact reset time from our side. Deleting and re-adding the domain isn't needed, so your client's DNS can stay as it is.
Status changed to Awaiting User Response Railway • 25 days ago
Status changed to Solved jordy241 • 25 days ago