24 days ago
Hi Railway team,
Our custom domain hq.zaki-solutions.com has been stuck on "Let's Encrypt rate limit reached. Please wait before retrying." (retryable: false) since 2026-10-23. Retrying gives the same message. No certificate has ever been issued for it, and we can't find a Let's Encrypt limit that fits, so we think the failure is cached or throttled on Railway's side.
DNS: Railway shows the CNAME and the ownership TXT record as verified and propagated. There is no CAA record, and no proxy or CDN in front.
Why we don't think it's a real Let's Encrypt limit:
- Certificate-transparency logs (crt.sh, Cert Spotter) show no certificate ever issued for this hostname. The only certificate under zaki-solutions.com is the apex (GitHub Pages, 2026-10-01), so neither the per-registered-domain nor the duplicate-certificate limit can have been reached.
- 2026-10-24: we deleted and re-added the domain, and it failed instantly. A name never used before on the same domain also failed instantly once verified.
- 2026-10-26: after waiting 33 hours we re-added it once, and it failed about 5 seconds later with the same message. That is too fast for a new ACME order.
- The hourly failed-validation limit would have refilled days ago, and the error has no Let's Encrypt unpause link.
Questions:
- What is the actual ACME error for this domain: which limit, and its Retry-After time?
- Is Railway returning a stored failure or applying its own throttle, rather than placing a new order?
- Can you clear it and issue the certificate? Or tell us when a retry will be allowed. We won't delete or re-add the domain again in the meantime.
Thank you!
2 Replies
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
We are working through these remaining ones and it will resolve in coming 6 hours
Status changed to Awaiting User Response Railway • 24 days ago
24 days ago
A new certificate has now been issued for your custom domain, and it shows as valid on our side. The domain was left exactly as it was, with the same CNAME target and verification record, so there is nothing to change in your DNS. If a browser still shows the old warning, that is a cached result and a fresh connection clears it.
Status changed to Solved dizzydes90 • 24 days ago