a month ago
Hello Railway Support,
I'm experiencing TLS certificate issuance failures for three custom domains in my project.
Project: vibrant-hope
Environment: production
Affected domains:
api.spartaco.com.br
control.spartaco.com.br
backoffice.spartaco.com.br
All domains are already verified and the DNS records are correctly configured.
For example, backoffice.spartaco.com.br currently shows:
Verified: yes
Sync status: ACTIVE
Certificate status: CERTIFICATE_STATUS_TYPE_ISSUE_FAILED
Certificate error: Let's Encrypt rate limit reached
Certificate error type: CERTIFICATE_ERROR_TYPE_RATE_LIMIT
Certificate retryable: false
The same Let's Encrypt rate-limit issue is affecting the other custom domains.
Could you please help with the certificate issuance once the rate limit allows it, or use another CA if that is possible?
I will avoid triggering additional certificate retries to prevent extending or hitting the rate limit again.
Thank you,
Matheus Jaconis
4 Replies
a month ago
We checked one of the three domains, and its DNS is propagated and ownership is verified. The certificate is failing only because the certificate authority is rate-limiting the name after repeated attempts. With a rate-limit failure, waiting is the only fix: a new attempt before the window clears will fail the same way. That's why the dashboard doesn't offer a retry button for this error. Holding off on retries, as you're already doing, is the right call.
Status changed to Awaiting User Response Railway • 26 days ago
a month ago
I have the same problem with two domains, is there any update?
Status changed to Awaiting Railway Response Railway • 26 days ago
Status changed to Awaiting User Response Railway • 26 days ago
25 days ago
Hello Railway Support,
Thank you for the clarification.
I understand that we need to wait for the Let's Encrypt rate limit to clear. However, this issue has already been blocking our custom domains for several days, so I would like to confirm whether there is anything Railway can do on your side to help.
I did not repeatedly trigger certificate issuance or retry attempts manually. The DNS records were configured and we waited for the normal verification and certificate issuance process.
Considering the platform instability and security incident Railway experienced around the same period, I’m wondering whether automatic certificate issuance attempts during that time may have contributed to reaching the Let's Encrypt rate limit.
Currently, the domains are correctly configured and verified, but certificate issuance remains blocked by the rate limit:
api.spartaco.com.br
control.spartaco.com.br
backoffice.spartaco.com.br
For example, the domain status shows:
Verified: yes
Sync status: ACTIVE
Certificate status: CERTIFICATE_STATUS_TYPE_ISSUE_FAILED
Certificate error: Let's Encrypt rate limit reached
Certificate error type: CERTIFICATE_ERROR_TYPE_RATE_LIMIT
Certificate retryable: false
We have intentionally stopped making any retry attempts to avoid extending or triggering the limit again.
Could you please check whether Railway can determine when the rate limit will clear, manually assist with the certificate issuance, or use another certificate authority if available?
Since these domains are required for our production environment, any assistance in resolving this as soon as possible would be greatly appreciated.
Thank you,
Matheus Jaconis
Status changed to Awaiting Railway Response Railway • 25 days ago
25 days ago
Apologies for the trouble, this related to an account issue today with our TLS certificate provider. We are back now, please click try again where the error arose in the UI. If this button doesn't regenerate it, please try removing the domain and adding again.
Status changed to Awaiting User Response Railway • 25 days ago
Status changed to Solved dizzydes90 • 25 days ago