Skip to content
SSL Generation Blocked: Let's Encrypt rate limit cache stuck on custom domain
Anonymous
OP

16 days ago

Hi support team,

I am experiencing an issue with the SSL certificate generation for my custom domain. The dashboard has been stuck with the error "Let's Encrypt rate limit reached" for more than 14 hours.

I have already verified that my DNS CNAME configuration for the subdomain is correctly pointing to my Railway default domain. Even after waiting out the standard Let's Encrypt cooldown period, the panel remains frozen with "retryable: false" and won't let me regenerate the TLS certificate.

Could you please clear the pending SSL generation cache on your side or manually trigger a retry for my domain?

Thank you for your help!

  • Domain with the issue: www.withaisolutions.com
  • Default Railway domain: wais-webpage-monolito-production.up.railway.app
Solved

4 Replies

Railway
BOT

16 days ago

Your domain's ownership verification is complete, and its CNAME now publicly resolves to the target Railway expects, so the DNS side is in place. The certificate failed because Let's Encrypt is rate-limiting this hostname after earlier failed validation attempts, and a rate-limit failure is one the platform does not retry automatically, which is why the dashboard shows it as non-retryable with no retry option.

There is no cache on our side holding this state: the limit is enforced by Let's Encrypt itself, and any new attempt made before its window clears fails the same way. Please leave the DNS records exactly as they are now and avoid removing and re-adding the domain, since that issues a new CNAME target and verification token and would mean redoing your DNS.


Status changed to Awaiting User Response Railway • 16 days ago


Anonymous
OP

16 days ago

Thank you for verifying that my DNS configuration is correct.

Since the DNS records are now perfectly set up and matching what Railway expects, I will follow your instructions and leave the domain and CNAME records exactly as they are without making any further changes.

Since the rate limit error has been active for more than 14 hours now, I will wait for Let's Encrypt's cooling window to clear. Could you please let me know if a manual trigger or an automatic retry will occur on your end once their window opens up, or if this ticket will remain open for a human agent to review if it doesn't auto-resolve?

Thank you!


Status changed to Awaiting Railway Response Railway • 16 days ago


Railway

Your domain's ownership verification is complete, and its CNAME now publicly resolves to the target Railway expects, so the DNS side is in place. The certificate failed because Let's Encrypt is rate-limiting this hostname after earlier failed validation attempts, and a rate-limit failure is one the platform does not retry automatically, which is why the dashboard shows it as non-retryable with no retry option. There is no cache on our side holding this state: the limit is enforced by Let's Encrypt itself, and any new attempt made before its window clears fails the same way. Please leave the DNS records exactly as they are now and avoid removing and re-adding the domain, since that issues a new CNAME target and verification token and would mean redoing your DNS.

Anonymous
OP

16 days ago

Thank you for verifying that my DNS configuration is correct.

Since the DNS records are now perfectly set up and matching what Railway expects, I will follow your instructions and leave the domain and CNAME records exactly as they are without making any further changes.

Since the rate limit error has been active for more than 14 hours now, I will wait for Let's Encrypt's cooling window to clear. Could you please let me know if a manual trigger or an automatic retry will occur on your end once their window opens up, or if this ticket will remain open for a human agent to review if it doesn't auto-resolve?

Thank you!


Railway
BOT

16 days ago

Nothing will retry on our end once Let's Encrypt's window clears, because a certificate that failed on a rate limit is not retried automatically. You can start a new attempt yourself with the CLI: run railway domain certificate retry followed by your domain, from the linked project. Your verification is complete and the CNAME publicly resolves to the target we expect, so a retry made after the window clears has what it needs on the DNS side.

Let's Encrypt's duplicate-certificate limit can block a domain for up to 7 days, so a retry made before that window clears will fail the same way. Waiting a little longer before you retry is safer than retrying right at the 14-hour mark.


Status changed to Awaiting User Response Railway • 16 days ago


Railway
BOT

9 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 • 9 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...