Skip to content
Custom domain certificate stuck on rate limit
glauciorgarcia-git
OP

a month ago

Custom domain certificate stuck on rate limit (project ism-app, service ism-app, production).

▎ Yesterday, admin.sofiamateus.com.br failed certificate issuance several times while its TXT verification record was wrong. Since then it has been stuck on "Let's Encrypt rate limit reached. Please wait before retrying", with "Certificate retryable: false". railway domain certificate retry refuses it too.

▎ Today I removed that domain and added backoffice.sofiamateus.com.br. DNS is correct (CNAME → 1t0mrblt.up.railway.app plus the TXT), and it verified at 13:11 UTC. Certificate issuance then failed immediately with the same rate-limit error.

▎ crt.sh shows no recent Let's Encrypt certificates for sofiamateus.com.br, so the limit doesn't seem to be on Let's Encrypt's side. Could you reset the issuance block and retry backoffice.sofiamateus.com.br? app.sofiamateus.com.br in the same service has a valid certificate.

Solved

5 Replies

Railway
BOT

a month ago

The new domain's DNS and ownership verification are both in place on our side: the CNAME matches its required target and the domain is verified. Its certificate, though, is currently in a failed state with the rate-limit error, which is the one certificate failure that is not retried automatically and has no retry option, because a new attempt made before the rate-limit window clears fails the same way.

Removing and re-adding the domain under a different name does not get around it, as you saw. Waiting out the window is the remedy for this state, and the other domain on the service with a valid certificate is not affected.


Status changed to Awaiting User Response Railway • 26 days ago


glauciorgarcia-git
OP

a month ago

Thanks. Two questions, could you escalate to a human? (1) How long is the rate-limit window in this case, so I don't trigger it again? (2) Once it clears, will the certificate be retried automatically, or do I need to remove and re-add backoffice.sofiamateus.com.br? If someone can reset it on your side, that would be appreciated.


Status changed to Awaiting Railway Response Railway • 26 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


dizzydes90

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.

glauciorgarcia-git
OP

25 days ago

Thanks! Clicking "try again" worked: the certificate was issued and the domain is serving HTTPS correctly now. All good on our side, you can close this ticket.


Status changed to Awaiting Railway Response Railway • 25 days ago


dizzydes90
EMPLOYEE

25 days ago

Glad that did it. Thanks for confirming, closing this one out.


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