Skip to content
Custom domain certificate stuck on “Let’s Encrypt rate limit reached” for 2+ days
tinezmatias
OP

25 days ago

Hi! The certificate for one of my custom domains has been stuck since Oct 25 and Railway doesn't let me retry it.

  • Domain: stg.meta.cocostylecba.com
  • Project: ba7b6f19-d17e-4bf5-9d2b-a17f227340ab
  • Environment: staging · Service: conn-meta
  • Domain ID: 6e89096d-1b1f-482e-a8b9-d29faf228119

Status: CERTIFICATE_STATUS_TYPE_ISSUE_FAILED, "Let's Encrypt rate limit reached. Please wait before retrying." (marked not retryable).

DNS is correct: CNAME stg.meta → nu0jyvv0.up.railway.app, shown as propagated and verified in the dashboard. There are no CAA records on cocostylecba.com.

I deleted and re-created the domain a couple of times on Oct 25–26. Each time I got a new CNAME target, and the record has a 1h TTL, so I think those early validations failed against the old target and kept hitting the limit. Another subdomain, stg.api.cocostylecba.com, had the same error and issued fine after one re-create. stg.meta never recovered, even after more than 24h untouched.

Could you clear or retry the certificate issuance for this domain? Thanks!

Solved

3 Replies

Railway
BOT

25 days ago

The certificate for that domain failed because Let's Encrypt rate-limited the name after repeated failed attempts. Your DNS and ownership verification both check out on our side, so the records aren't the problem.

The dashboard has no retry for this error, and neither we nor you can clear Let's Encrypt's limit early. Any new attempt made before their window clears gets rate-limited again. Please don't delete and re-create the domain while you wait: that gives you a new CNAME target and starts more failed attempts against the same name.


Status changed to Awaiting User Response Railway • 25 days ago


Railway

The certificate for that domain failed because Let's Encrypt rate-limited the name after repeated failed attempts. Your DNS and ownership verification both check out on our side, so the records aren't the problem. The dashboard has no retry for this error, and neither we nor you can clear Let's Encrypt's limit early. Any new attempt made before their window clears gets rate-limited again. Please don't delete and re-create the domain while you wait: that gives you a new CNAME target and starts more failed attempts against the same name.

tinezmatias
OP

25 days ago

Thanks, that makes sense — I won't touch the domain. Two quick questions:

  1. Once Let's Encrypt's window clears, will Railway retry the issuance automatically, or do I need to trigger something (the dashboard shows it as not retryable)?
  2. Roughly how long is that window for this case, so I know when to check back?

Status changed to Awaiting Railway Response Railway • 25 days ago


dizzydes90
EMPLOYEE

24 days ago

Apologies for the trouble, this related to an account issue yesterday with our TLS certificate provider. We are back now, please click try again where the error arose in the UI. If this button doesn't regenerate it, please try removing the domain and adding again.


Status changed to Awaiting User Response Railway • 24 days ago


Status changed to Solved dizzydes90 • 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...