a month ago
Railway reports verified custom-domain ownership, CERTIFICATE_STATUS_TYPE_ISSUE_FAILED, the error "Let's Encrypt rate limit reached. Please wait before retrying.", and retryable=false.
The existing first-level custom hostname has the correct Railway CNAME behind Cloudflare. Edge HTTPS works with Full, following Railway's documentation, while the origin certificate still does not match the custom hostname. Cloudflare Access must remain enabled. During this investigation we have not deleted/recreated the domain or retried certificate issuance.
Where can we read the underlying CA rate-limit category and exact retry-after/reset time? After the cooldown, will Railway resume automatically, or does support need to make retry available again? Is any ACME-specific action needed while retaining Cloudflare Access?
We reviewed the SSL documentation and the existing rate-limit discussion. The remaining question is how to determine when one safe retry is appropriate from the current non-retryable status. This is a platform-status question; no customer data, secrets or private project identifiers are included.
3 Replies
a month ago
We don't expose the certificate authority's rate-limit category or an exact retry-after or reset time for this error, so there is no field or dashboard view that will tell you when the window clears. What the rate-limit failure does mean is that a new attempt made before the window clears will fail again, so waiting is the only remedy for now.
This failure type is one the platform does not retry automatically, which is why the dashboard shows that it cannot be automatically retried and offers no Try Again control for it. The current failed order will not resume on its own once the cooldown passes; getting a certificate requires a fresh certificate order after the window has cleared. Please don't remove and re-add the domain to force one, since that issues a new CNAME target and verification token and is itself another attempt against the limit.
On the ACME side, non-wildcard domains are validated over HTTP-01: the certificate authority fetches a token over plain HTTP at /.well-known/acme-challenge/ on your hostname, from several network locations. Cloudflare Access can stay enabled for the rest of the site, but that path has to reach us without an Access login or redirect in front of it, otherwise the next fresh order will fail validation the same way.
Status changed to Awaiting User Response Railway • 27 days ago
Railway
We don't expose the certificate authority's rate-limit category or an exact retry-after or reset time for this error, so there is no field or dashboard view that will tell you when the window clears. What the rate-limit failure does mean is that a new attempt made before the window clears will fail again, so waiting is the only remedy for now. This failure type is one the platform does not retry automatically, which is why the dashboard shows that it cannot be automatically retried and offers no Try Again control for it. The current failed order will not resume on its own once the cooldown passes; getting a certificate requires a fresh certificate order after the window has cleared. Please don't remove and re-add the domain to force one, since that issues a new CNAME target and verification token and is itself another attempt against the limit. On the ACME side, non-wildcard domains are validated over HTTP-01: the certificate authority fetches a token over plain HTTP at `/.well-known/acme-challenge/` on your hostname, from several network locations. Cloudflare Access can stay enabled for the rest of the site, but that path has to reach us without an Access login or redirect in front of it, otherwise the next fresh order will fail validation the same way.
a month ago
Thanks. Please clarify the supported operation for a fresh certificate order after the cooldown when retryable=false and no Try Again control exists. Which Railway action or staff intervention preserves the existing domain, CNAME target and verification token? A human confirmation of that operation would help us avoid another failed issuance attempt. We will keep the current Access controls and SSL mode while waiting.
Status changed to Awaiting Railway Response Railway • 27 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.
One thing specific to your setup: Cloudflare Access currently answers the ACME path on that hostname with its login page, and the certificate order can't validate through it. Add an Access bypass policy for /.well-known/acme-challenge/* (Access can stay on for everything else), or proxy the hostname off while the certificate issues, then retry.
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