Skip to content
Custom domain certificates stuck on "Let's Encrypt rate limit reached" (not retryable)
nispot
OP

25 days ago

Hi! TLS certificates for two custom domains failed and Railway marks them as not retryable. It looks like the same issue as https://station.railway.com/questions/custom-domain-certificate-stuck-on-let-dcf972f2

Project: Overdrive (6a013b27-0ef8-41cd-a73e-0eca8ba0afb7)

Environment: production (c7f57113-d6a0-4d51-b935-bc0c54ee0751)

Service: decknik-review-web (91b700c8-6fe6-439d-ae27-ae5c0fc9c4e5)

Domain decknik.com: e2c36c6b-0e03-4b8c-b5f2-047255aabd5f, CNAME (flattened) to 4l2agb5k.up.railway.app

Domain www.decknik.com: c8dbc38d-9874-4713-a614-a4ccfdf6232c, CNAME to f0scf4yb.up.railway.app

Status on both: CERTIFICATE_STATUS_TYPE_ISSUE_FAILED, "Let's Encrypt rate limit reached. Please wait before retrying. This error cannot be automatically retried."

DNS is on Cloudflare (DNS only, not proxied), with no CAA records. The dashboard shows both domains as verified and the DNS records as propagated, and the _railway-verify TXT records are in place. Right now the domain serves the default *.up.railway.app certificate, so browsers reject it.

Could you clear the rate-limit state and retry issuance for both domains? Thanks!

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 25 days ago


dizzydes90
EMPLOYEE

25 days ago

Apologies for the trouble, this related to an account issue today 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 • 25 days ago


Status changed to Solved dizzydes90 • 25 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...