25 days ago
We added eight custom domains (subdomains of one apex domain) to services in one project. One got a certificate. Six failed with "Let's Encrypt rate limit reached" on Oct 23 and are still failing, marked not retryable, and one is stuck validating ownership. The services still work on their *.up.railway.app URLs, but we can't move to our domain. Could Railway check which rate limit is being hit and re-queue issuance?
Resources
- Project ID: d694eecd-0129-4764-8a07-40135caa826a. The domains are listed on its services, in two environments.
- 6 domains: CERTIFICATE_ERROR_TYPE_RATE_LIMIT, retryable: false.
- 1 domain (api.testnet. on the testnet environment): stuck in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP, verified: false, even though its _railway-verify TXT record is published.
- 1 domain (app. on production): VALID.
- Created 2026-10-23 around 15:32 UTC. Last checked 2026-10-26 17:18 UTC, unchanged.
Error (from railway domain status --json, CLI 5.26.0):
"status": "CERTIFICATE_STATUS_TYPE_ISSUE_FAILED",
"errorMessage": "Let's Encrypt rate limit reached. Please wait before retrying.",
"errorType": "CERTIFICATE_ERROR_TYPE_RATE_LIMIT",
"retryable": false
What We Tried
- DNS: CNAME and TXT records are at GoDaddy. Railway shows every CNAME as DNS_RECORD_STATUS_PROPAGATED and every domain except one as verified: true. Public resolvers return theexpected values. There are no CAA records and no DNSSEC.
- Possible cause (unconfirmed): the records went in while a nameserver change was still in progress, so early validations may have failed.
- Retry: railway domain certificate retry returns Certificate retry is not available for this failure.
- Re-adding: we deleted and re-added one domain (on Oct 23 and on Oct 26 at 14:38 UTC) and updated its CNAME to the new target. It verified, then failed straight away with the same rate-limit error.
- Certificate history: crt.sh lists only 4 certificates ever issued for the apex domain, so our own volume shouldn't have hit a per-domain limit.
We haven't changed anything else and don't need anything deleted. We can share the domain names privately if needed.
1 Reply
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
