a month ago
Hello,
I need help with TLS certificate issuance for the tlt-transport service.
Custom domains:
- tlttransport.nl
- www.tlttransport.nl
Both domains are connected to Railway and the DNS records have already propagated correctly.
Current DNS configuration:
- Root domain: ALIAS to the Railway target
- www: CNAME to the Railway target
- Railway verification TXT records are present
I verified the records using the authoritative Vimexx nameserver, Cloudflare DNS (1.1.1.1), and Google DNS (8.8.8.8).
The application itself is deployed and working correctly at:
https://tlt-transport-production.up.railway.app/
However, Railway now shows the following error for both custom domains:
“Failed to issue TLS certificate — Let’s Encrypt rate limit reached. Please wait before retrying. This error cannot be automatically retried.”
The DNS configuration is stable now and I have not been repeatedly changing the records.
Could you please check:
- Which Let’s Encrypt rate limit has been reached?
- When certificate issuance can safely be attempted again.
- Whether Railway will retry automatically when the limit resets.
- If not, what exact manual action I should take after the reset.
- Whether certificate issuance can be retried or assisted from Railway’s side.
I would prefer not to remove and re-add the domains unnecessarily, as I do not want to trigger further certificate attempts before the rate limit has cleared.
The production website is ready; valid TLS on the custom domains is the only remaining blocker.
Thank you.
8 Replies
a month ago
Both custom domains show ownership verified and their DNS records propagated, and both certificates are in a failed state with a Let's Encrypt rate-limit error. That error means the certificate authority is limiting new orders for these names after earlier failed attempts, and the error itself does not say which specific limit was hit or exactly when it resets.
Waiting for the rate-limit window to clear is the only remedy for this error type, and a new attempt made before it clears fails the same way. This error is not retried automatically, which is why the dashboard does not show a Try Again button for it the way it does for other certificate failures.
You are right not to remove and re-add the domains. That would issue new CNAME targets and verification tokens, forcing you to redo your DNS, and it would not get around the rate limit.
Status changed to Awaiting User Response Railway • 26 days ago
a month ago
i reccomend waiting 24 hrs then re adding the domain, as the bot just said above railway does not automatically or manually retry it, so the only way to force it through would be to re add it.
Status changed to Awaiting Railway Response Railway • 26 days ago
Status changed to Awaiting User Response Railway • 26 days ago
saerio
i reccomend waiting 24 hrs then re adding the domain, as the bot just said above railway does not automatically or manually retry it, so the only way to force it through would be to re add it.
a month ago
Hi saerio, thanks for your suggestion!
Just to clarify, have you personally experienced this exact Let's Encrypt rate-limit error on Railway and successfully resolved it by removing and re-adding your custom domain?
If so, how long did you wait before trying again, and did you have to update your DNS records afterward?
I'm asking because both of my domains are already verified and propagated, and I want to avoid triggering additional failed certificate attempts or disrupting the existing configuration.
I'd really appreciate hearing what worked in your case. Thanks!
Status changed to Awaiting Railway Response Railway • 26 days ago
a month ago
Both domains still show ownership verified, DNS propagated, and the certificate failed with the Let's Encrypt rate-limit error.
As our earlier reply mentioned, removing and re-adding a custom domain gives it a new CNAME target and a new verification token, so you would need to update your DNS records again. It also does not get around the rate limit, and an attempt made before the window clears fails the same way.
Status changed to Awaiting User Response Railway • 26 days ago
dark04phoenix
Hi saerio, thanks for your suggestion! Just to clarify, have you personally experienced this exact Let's Encrypt rate-limit error on Railway and successfully resolved it by removing and re-adding your custom domain? If so, how long did you wait before trying again, and did you have to update your DNS records afterward? I'm asking because both of my domains are already verified and propagated, and I want to avoid triggering additional failed certificate attempts or disrupting the existing configuration. I'd really appreciate hearing what worked in your case. Thanks!
a month ago
No, i have not, when re-adding a domain you will however have to re-add the DNS records, But as the bot said, railway doesnt automatically retry this error, so it is basically your only choice,
I fear there is no better response to be gotten.
Status changed to Awaiting Railway Response Railway • 26 days ago
Status changed to Awaiting User Response Railway • 26 days ago
a month ago
I feel the need to reitterate: to WAIT before doing this.
removing and readding the domain too early will extend lets encrypts rate limit on your domain.
and as this is an issue on lets encrypt's side railway staff cannot help you bypass it
Status changed to Awaiting Railway Response Railway • 26 days ago
Status changed to Awaiting User Response Railway • 26 days ago
25 days ago
I have an update for you: this is now a known issue to railway, and railway is in talks with letsencrypt on fixing it. More on status.railway.com
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
saerio
I have an update for you: this is now a known issue to railway, and railway is in talks with letsencrypt on fixing it. More on status.railway.com
25 days ago
Thanks a lot for the update, I really appreciate it. You were actually the first one to let me know that Railway had officially acknowledged the TLS issue. Hopefully now that they’re working directly with Let’s Encrypt, we see some progress soon and I get my TLC certificates 🙏🏼
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
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