25 days ago
Custom domains both fail with: "Failed to issue TLS certificate - Let's Encrypt rate limit
reached. This error cannot be automatically retried."
DNS is correct (CNAME and _railway-verify TXT resolve publicly, DNS is hosted
at OVH, no Cloudflare proxy). First failure around 11:01 CET on 2026-10-26,
still failing 6 hours later with a different hostname.
is there any cooldown time for retries?
2 Replies
25 days ago
Both of your domains show ownership verified and the routing CNAME resolving to the right target, so DNS is not what is blocking them now. The failure on each is a Let's Encrypt rate limit, which the certificate authority applies to a name after repeated failed attempts.
That is why the dashboard shows no retry for it: waiting for the window to clear is the only remedy, and any new attempt made before then fails the same way. Let's Encrypt sets those windows, so we can't give you an exact cooldown, but holding off on further retries for these names keeps them from being extended.
Status changed to Awaiting User Response Railway • 25 days ago
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
A new certificate has now been issued for the custom domain that was failing, and every custom domain on that service now shows a valid certificate. The domains were left exactly as they were, with the same DNS targets and verification records, so there is nothing to update in your DNS, and HTTPS is serving on each hostname. If a browser still shows the old warning, that is a cached result and a fresh connection clears it.
There is no cooldown left to wait out and nothing for you to retry. Your DNS was correct throughout; the failure was not caused by anything on your domains.
Status changed to Awaiting User Response dizzydes90 • 24 days ago
Status changed to Solved dizzydes90 • 24 days ago