Skip to content
TLS certificate failed: "Let's Encrypt rate limit reached" on custom domain
lmpagency
OP

25 days ago

Hi, I added two custom domains to my service listmyproject-site:

DNS is at Spaceship and everything is verified:

  • @ CNAME -> kvnj7o0b.up.railway.app (flattened by Spaceship; apex A resolves to 69.46.46.16, same as the Railway target)
  • www CNAME -> f4l9x4wo.up.railway.app
  • _railway-verify and _railway-verify.www TXT records are green
  • DNSSEC is enabled and validates correctly (Verisign analyzer all green)

Both domains show:

"Failed to issue TLS certificate · Let's Encrypt rate limit reached.

This error cannot be automatically retried."

The first issuance attempts likely happened before the DNS records were in place.

The edit dialog only allows changing the port, so I can't trigger a retry myself.

Could you please retry certificate issuance for both domains?

Thanks!

Solved

3 Replies

Railway
BOT

25 days ago

Both domains show as verified and their routing records are in place on our side. The certificates failed because Let's Encrypt is rate-limiting these names after the earlier failed attempts, which likely happened before your records were set up. Unlike other certificate failures, this one has no retry button: waiting for Let's Encrypt's rate-limit window to clear is the only fix, and any new attempt made before then fails the same way.

Please don't remove and re-add the domains to force a retry. That gives them a new CNAME target and verification token, so you would have to update your DNS again.


Status changed to Awaiting User Response Railway • 25 days ago


Railway

Both domains show as verified and their routing records are in place on our side. The certificates failed because Let's Encrypt is rate-limiting these names after the earlier failed attempts, which likely happened before your records were set up. Unlike other certificate failures, this one has no retry button: waiting for Let's Encrypt's rate-limit window to clear is the only fix, and any new attempt made before then fails the same way. Please don't remove and re-add the domains to force a retry. That gives them a new CNAME target and verification token, so you would have to update your DNS again.

lmpagency
OP

25 days ago

Thanks. The failed attempts were made over a day ago, so the Let's Encrypt window

(failed validations reset hourly) should already be clear.

Since there is no retry button and the error says it cannot be automatically retried,

how will a new issuance attempt be triggered? Could a Railway team member please

re-queue certificate issuance for listmyproject.ai and www.listmyproject.ai?


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