Skip to content
Unable to add custom domain because of Lets Encrypt rate limit.
tanmaybhayani
OP

25 days ago

Getting this error when trying to setup custom domain.

Failed to issue TLS certificate

Let's Encrypt rate limit reached. Please wait before retrying.

This error cannot be automatically retried. Please check your DNS configuration or contact support.

Solved

6 Replies

Railway
BOT

25 days ago

Your domain's DNS is set up correctly and ownership is verified, so nothing needs to change on your side. The certificate failed because Let's Encrypt is temporarily rate-limiting new certificates for that name after repeated failed attempts.

The only fix is to wait for that rate-limit window to clear. Any new attempt before then will fail the same way, and removing and re-adding the domain won't help.


Status changed to Awaiting User Response Railway • 25 days ago


Railway

Your domain's DNS is set up correctly and ownership is verified, so nothing needs to change on your side. The certificate failed because Let's Encrypt is temporarily rate-limiting new certificates for that name after repeated failed attempts. The only fix is to wait for that rate-limit window to clear. Any new attempt before then will fail the same way, and removing and re-adding the domain won't help.

tanmaybhayani
OP

25 days ago

By when can I expect this rate-limit issue to be resolved?


Status changed to Awaiting Railway Response Railway • 25 days ago


Railway
BOT

25 days ago

We can't give an exact time. The rate-limit error we have on record doesn't say when the window ends, and the certificate authority sets that window, not us.

Your DNS and ownership verification both still check out, so nothing needs to change on your side. Any attempt made before the window clears will fail the same way.


Status changed to Awaiting User Response Railway • 25 days ago


Railway

We can't give an exact time. The rate-limit error we have on record doesn't say when the window ends, and the certificate authority sets that window, not us. Your DNS and ownership verification both still check out, so nothing needs to change on your side. Any attempt made before the window clears will fail the same way.

tanmaybhayani
OP

25 days ago

I need an estimate. I cant wait forever.


Status changed to Awaiting Railway Response Railway • 25 days ago


Railway
BOT

25 days ago

We understand the wait is frustrating, but we don't have a concrete estimate to give. The certificate authority sets the rate-limit window, and the error on your domain doesn't say when it ends.

We checked again just now. Your DNS record is still correct and ownership is still verified, but the certificate is still blocked by the rate limit. Nothing needs to change on your side, and retrying or removing and re-adding the domain before the window clears will fail the same way.


Status changed to Awaiting User Response Railway • 25 days ago


Status changed to Awaiting Railway Response Railway • 25 days ago


dizzydes90
EMPLOYEE

25 days ago

A new certificate has now been issued for your custom domain. The domain was left exactly as it was, with the same CNAME target and verification record, so there is nothing to update in your DNS, and HTTPS is serving on the hostname. If a browser still shows the old warning, that is a cached result and a fresh connection clears it.

Sorry for the frustration this caused. Your DNS was correct throughout; the failure was not caused by anything on your domain.


Status changed to Awaiting User Response dizzydes90 • 25 days ago


Status changed to Solved dizzydes90 • 25 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...