25 days ago
Hello Railway Community!
I'm experiencing an SSL/TLS certificate issuance issue with one of my services on Railway.
Project: elunalab
Environment: production
Service: continuar-whatsapp
Custom domain: continuar-whatsapp.elunalab.com.br
Error message
"Failed to issue TLS certificate. Let's Encrypt rate limit reached. Please wait before retrying. This error cannot be automatically retried. Please check your DNS configuration or contact support."
Additional information
- This is the only service experiencing this issue.
- All other services and custom domains in the same Railway project are working correctly.
- The affected service is online and running successfully.
- The issue appears to be specifically related to SSL/TLS certificate issuance for this custom domain.
- I'm currently using the Railway Hobby plan.
Questions
- Is there a way to manually retry certificate issuance after the Let's Encrypt rate limit expires?
- Could this be caused by an incorrect DNS configuration, even though my other custom domains work correctly?
- Is there a recommended solution that doesn't require deleting and recreating the custom domain?
- Can Railway support manually reset or retry the certificate issuance?
This service is part of a production application with active customers, so I'm looking for a solution that minimizes downtime.
Any guidance from the Railway team or community would be greatly appreciated!
Thank you!
Élida — ELUNA Lab
2 Replies
25 days ago
Your DNS for that domain is correct: the CNAME is propagated to the right target and ownership is verified, so this isn't a DNS misconfiguration. The failure is a rate limit from the certificate authority, which kicks in after repeated failed issuance attempts for the same name, and waiting for that window to clear is the only remedy; a new attempt before then will fail the same way.
There's no need to delete and recreate the domain, and doing so would give you a new CNAME target and verification token to set up again, so keep the existing records as they are.
Status changed to Awaiting User Response Railway • 25 days ago
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
A new certificate has now been issued for your custom domain. The domain was left exactly as it was, with the same CNAME target and verification record, so there is nothing to update in your DNS, and HTTPS is serving on the hostname. If a browser still shows the old warning, that is a cached result and a fresh connection clears it.
Your DNS was correct throughout; the failure was not caused by anything on your domain.
Status changed to Awaiting User Response dizzydes90 • 24 days ago
Status changed to Solved dizzydes90 • 24 days ago