an hour ago
Hello Railway Support,
I'm having an issue with the custom domain "dash.vexobot.qd.je" on my project.
Railway shows the following error:
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."
My app
lication is running on port 3000, and the default Railway domain is working. However, the custom domain still doesn't have a valid TLS certificate.
I previously configured this custom domain and DNS records, but the certificate issuance failed due to the rate limit. I would appreciate your help identifying the cause and resolving the issue.
Could you please check whether the certificate can be reissued, or advise me on the exact DNS changes needed to get HTTPS working?
I have attached a screenshot of the error.
Thank you for your help.
Attachments
1 Replies
an hour ago
Your domain is verified, but the certificate was refused because Let's Encrypt's rate limit for it was reached, so a new certificate can only be issued after that limit window passes.
Separately, the CNAME record we last saw for the domain points at an older Railway target, not the one it currently needs, and a public lookup right now returns no CNAME for it at all. In your DNS provider, set the CNAME for that subdomain to the exact target shown for the domain in the service's Networking settings, and avoid repeatedly deleting and re-adding the domain on Railway, since each re-add creates a new target and adds to the same rate limit.
Status changed to Awaiting User Response Railway • about 1 hour ago