24 days ago
Our website www.basic.cv was configured on Railway on 26 October 2026.
The application is online and works correctly through the Railway-generated address:
https://basic-cv-production.up.railway.app
However, the custom domain is not working.
Railway displays the following error:
"Failed to issue TLS certificate. Let's Encrypt rate limit reached. This error cannot be automatically retried."
The domain is registered with OLA.cv.
Our current CNAME record is:
www.basic.cv → z3dx5slj.up.railway.app
Please verify that the DNS configuration is correct and assist with retrying the SSL certificate issuance.
Could you also confirm whether the recent Railway infrastructure incident has contributed to this problem?
The website is ready for launch, but we cannot use our registered domain.
Thank you.
5 Replies
24 days ago
Your DNS is set up correctly. The CNAME points at the target we expect, the domain is verified, and the only thing blocking it is the certificate, which Let's Encrypt is currently rate-limiting after repeated failed attempts.
On 26 October, between about 19:18 and 20:02 UTC, we had an incident where TLS certificates were not generating for new or changed domains. It has since been resolved, and failed attempts from around that time may have added to the rate limit you are seeing now. You can see the full timeline here: TLS certificates not generating
This error cannot be retried automatically. The rate limit has to expire first, because any new attempt before then will fail the same way. You do not need to change your DNS records.
Status changed to Awaiting User Response Railway • 24 days ago
24 days ago
Thank you for confirming that our DNS configuration is correct and explaining the certificate issuance failure.
Could you please clarify two points?
-
When is the Let's Encrypt rate limit expected to expire for www.basic.cv?
-
As Railway confirms that the certificate cannot be retried automatically, will your team initiate the certificate request once the rate limit expires, or will I need to take action myself?
I would appreciate an estimated timeframe, as the website is ready to launch and is currently inaccessible through our registered domain.
Regards
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
The certificate is still in a failed state with the Let's Encrypt rate limit error, and we don't have an exact time for when that limit lifts. Your CNAME and domain verification are both still correct.
Retrying the certificate is a step you take yourself. Once the limit has lifted, you can retry issuance with the CLI by running railway domain certificate retry followed by your domain name, as described in the railway domain docs. If you retry before the limit lifts, it will fail with the same error.
Status changed to Awaiting User Response Railway • 24 days ago
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
A new certificate has now been issued for your www 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.
There is no rate-limit window left to wait out and nothing for you to retry. 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
24 days ago
Apologies for the trouble, this related to an account issue on October 26 with our TLS certificate provider, not your DNS. We are back now, so you don't need to wait for a window to expire: please click try again where the error arose in the UI for www.basic.cv. If this button doesn't regenerate the certificate, please try removing the domain and adding it again.
Status changed to Awaiting User Response Railway • 24 days ago
Status changed to Solved dizzydes90 • 24 days ago