Skip to content
Custom domain TLS certificate fails — "Let's Encrypt rate limit reached" on a hostname never used before
wbambano-code
OP

25 days ago

Hello,

Two custom domains on one of my services fail with:

"Failed to issue TLS certificate — Let's Encrypt rate limit reached. This error cannot be automatically retried."

  • DNS is verified: the CNAME and _railway-verify TXT records are in place and resolve on public resolvers. There is no CAA record.
  • No certificate has ever been issued for these hostnames.
  • One of them is a brand-new hostname that failed on its very first attempt, so it does not look like a limit triggered on my side.

Could a team member check the certificate issuance on their side? I can share the domain names and project privately if needed. I will not remove or re-add the domains in the meantime.

Thank you.

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...