Skip to content
TLS certificate
mrmassaw
OP

25 days ago

Hi, my custom domain torch-e.com has no TLS certificate. The domain was bought through Railway, and DNS is verified. The certificate first failed with “Let’s Encrypt rate limit reached”. Overnight it failed with “An internal error occurred”. A retry today hit the Let’s Encrypt rate limit again. I first added the domain to the wrong service (torch-burner) by mistake and then moved it to torch-e, which may have used up the attempts. Could you check which limit is blocking it and issue the certificate? Thanks!

Solved

1 Reply

Railway
BOT

25 days ago

The block right now is Let's Encrypt's own rate limit on that name, which it applies after repeated issuance attempts, and the moves between services plus the retries plausibly counted toward it. The overnight "internal error" was a generic failure message and is not what is stopping issuance now; your ownership verification and routing record both check out on our side.

Waiting is the only remedy for this limit. Any new attempt made before the window clears, from your side or ours, fails the same way and keeps the limit in place, so hold off on retries and changes to the domain for now. Once the window has cleared, a fresh certificate attempt is what the domain needs, and there is no need to remove and re-add it or change its DNS.


Status changed to Awaiting User Response Railway • 25 days ago


Railway
BOT

18 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 • 18 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...