24 days ago
Custom domain bots.colmenatrading.com, project prop-farmer, environment development.
Certificate status has been ISSUE_FAILED with "Let's Encrypt rate limit reached" for 20+ hours. The domain is verified and the CNAME is propagated. There are no CAA records and DNSSEC is off.
Early failures happened because a wildcard record caught bots before its CNAME existed; bots now has an explicit CNAME that overrides it.
Could a Railway team member please check which limit is active and retrigger issuance without changing the DNS values? The retry API refuses to retry.
Thanks!
1 Reply
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
A new certificate has now been issued for your custom domain, and it shows as valid on our side. The domain was left exactly as it was, with the same CNAME target and verification record, so there is nothing to change in your DNS. If a browser still shows the old warning, that is a cached result and a fresh connection clears it.
Status changed to Awaiting User Response Railway • 24 days ago
Status changed to Solved dizzydes90 • 24 days ago