Skip to content
Failed to issue TLS certificate
sparksx
OP

24 days ago

Custom domains both fail with: "Failed to issue TLS certificate - Let's Encrypt rate limit reached. This error cannot be automatically retried."

DNS is correct (CNAME and _railway-verify TXT resolve publicly, DNS is hosted at OVH with Cloudflare proxy). First failure around 2026-10-25, still failing for two domains on my beta env.

is there any cooldown time for retries?

Solved

6 Replies

sparksx
OP

24 days ago

This is happening for two different services (both on beta env)*


Railway
BOT

24 days ago

We checked both of the failing beta domains: their CNAME records point at the correct targets, ownership is verified, and requests to the certificate challenge path reach our edge. The certificates stopped because Let's Encrypt is rate-limiting those hostnames after repeated failed attempts. Your other beta domains have valid certificates.

There is no cooldown you can skip. Waiting for the limit to clear is the only fix, and a new attempt before then will fail the same way. We can't give you an exact time because Let's Encrypt sets the window, not us.


Status changed to Awaiting User Response Railway • 24 days ago


Railway

We checked both of the failing beta domains: their CNAME records point at the correct targets, ownership is verified, and requests to the certificate challenge path reach our edge. The certificates stopped because Let's Encrypt is rate-limiting those hostnames after repeated failed attempts. Your other beta domains have valid certificates. There is no cooldown you can skip. Waiting for the limit to clear is the only fix, and a new attempt before then will fail the same way. We can't give you an exact time because Let's Encrypt sets the window, not us.

sparksx
OP

24 days ago

Im blocked since multiple days now, I assume I need a human touch at this point to be unlocked


Status changed to Awaiting Railway Response Railway • 24 days ago


dizzydes90
EMPLOYEE

24 days ago

Apologies for the trouble, this related to an account issue on October 26 with our TLS certificate provider, not your DNS. We are back now, so you don't need to wait for a window to expire: please click try again where the error arose in the UI. If this button doesn't regenerate the certificate, please try removing the domain and adding it again.


Status changed to Awaiting User Response Railway • 24 days ago


Status changed to Solved dizzydes90 • 24 days ago


Status changed to Awaiting Railway Response dizzydes90 • 24 days ago


dizzydes90
EMPLOYEE

24 days ago

Update on this: it's on our side, and we'll fix it for you. We're reissuing the certificate for your domain within the next 12 hours. Please leave the domain, its CNAME and the verification record exactly as they are; there's no need to remove and re-add it or to click retry.


Status changed to Awaiting User Response Railway • 24 days ago


dizzydes90
EMPLOYEE

24 days ago

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


Status changed to Solved dizzydes90 • 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...