Skip to content
TLS Certificate Issuance Failed – Let's Encrypt Rate Limit
bintaleb86
OP

25 days ago

Hello Railway Support,

I'm experiencing an SSL/TLS certificate issuance issue with my custom domain.

Project: Emma-platform

Environment: staging

Service: Emma-platform

Custom domain: www.emmamandiri.com

Railway-generated domain: emma-platform-staging.up.railway.app

The DNS CNAME is configured as follows:

www.emmamandiri.com → b8kautux.up.railway.app

The TXT verification record has been successfully verified, and DNSChecker confirms that the CNAME has propagated across multiple DNS resolvers.

However, Railway displays the following error:

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

Could you please investigate the certificate issuance failure and advise when and how the certificate can be retried? If possible, please help initiate a new issuance attempt once the rate limit permits.

The root domain emmamandiri.com is also pending DNS configuration, but our immediate priority is getting www.emmamandiri.com working securely over HTTPS.

Thank you for your assistance.

Solved

2 Replies

Railway
BOT

25 days ago

Your CNAME and TXT verification records are both correct and verified on our side, so DNS is not the cause. The certificate failed because Let's Encrypt is rate-limiting this hostname after repeated issuance attempts.

Waiting for that rate-limit window to clear is the only remedy, and a new attempt made before it clears will fail the same way.


Status changed to Awaiting User Response Railway • 25 days ago


Status changed to Awaiting Railway Response Railway • 24 days ago


dizzydes90
EMPLOYEE

24 days ago

A new certificate has now been issued for your www custom domain. It was left exactly as it was, with the same CNAME target and verification record, and HTTPS is serving on it. If a browser still shows the old warning, that is a cached result and a fresh connection clears it.

The apex domain is a separate case: it is still waiting on the DNS records shown for it in the service's Networking settings, and ownership has not verified yet, so no certificate attempt has run for it. Once those records are in place it will verify and issue on its own.

For www, your DNS was correct throughout; that failure was not caused by anything on your domain.


Status changed to Awaiting User Response dizzydes90 • 24 days ago


Railway
BOT

17 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 17 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...