2 hours ago
Custom domain: panel.johaaletrader.com
Railway reports ownership verified, CNAME propagated, target port 3000, CERTIFICATE_STATUS_TYPE_ISSUE_FAILED, "Let's Encrypt rate limit reached. Please wait before retrying.", and retryable:false. The dashboard also says: "This error cannot be automatically retried. Please check your DNS configuration or contact support."
Independent checks on 2026-10-26 at 05:42 UTC:
- Cloudflare (1.1.1.1) and Google (8.8.8.8) both return the expected CNAME: d37bgy3i.up.railway.app.
- The root domain has no CAA records returned and no DS record returned.
- HTTPS to the custom hostname fails normal certificate verification with a hostname mismatch.
- The existing Railway hostname passes certificate verification and /healthz returns HTTP 200.
- crt.sh returned zero records for the exact hostname. This does not establish which ACME limit was reached.
- No repeated domain removal/recreation has been performed during this investigation.
Please have a Railway platform operator:
- Inspect the original ACME order/error and identify the exact rate-limit category.
- Provide the authoritative Retry-After timestamp, or an unpause/recovery instruction if applicable.
- Check why the domain is non-retryable and whether issuance must be resumed/requeued when eligible.
- Confirm the supported recovery action without deleting/recreating the domain or interrupting the existing Railway hostname.
I can provide internal project/service/domain identifiers through private support. No credentials or private identifiers are included here.
1 Replies
2 hours ago
Your DNS is set up correctly: the traffic CNAME has propagated and domain ownership is verified. The certificate failed because Let's Encrypt has rate-limited this hostname, so nothing about your configuration needs to change.
With a rate-limit failure, waiting for the window to clear is the only fix. A new attempt before then fails the same way, which is also why the dashboard doesn't offer a retry button for this error. Don't remove and re-add the domain. That gives you a new CNAME target and verification token, so you'd have to redo your DNS, and the rate limit would still apply.
Status changed to Awaiting User Response Railway • about 2 hours ago