Skip to content
www.meditask.co.uk TLS issuance failed after DNS verification (Let's Encrypt rate limit)
eliminate-entrant
OP

a month ago

The custom domain www.meditask.co.uk is verified, and Railway now reports its DNS as DNS_RECORD_STATUS_PROPAGATED. Both authoritative nameservers (ns75.domaincontrol.com and ns76.domaincontrol.com), Google DNS and Cloudflare DNS return the required CNAME: www.meditask.co.uk -> r0lhn1ih.up.railway.app.

Certificate issuance remains stuck with:

  • certificateStatus: CERTIFICATE_STATUS_TYPE_ISSUE_FAILED
  • certificateErrorType: CERTIFICATE_ERROR_TYPE_RATE_LIMIT
  • certificateErrorMessage: Let's Encrypt rate limit reached. Please wait before retrying.
  • certificateRetryable: false
  • certificates: []

The dashboard says this error cannot be automatically retried. A direct HTTPS check against Railway's IP fails hostname certificate validation for www.meditask.co.uk. The app itself is healthy at https://meditaskwebsite-production.up.railway.app.

DNS was moved from Wix to 123 Reg today (25 October 2026). The unused apex-domain attachment has been removed; 123 Reg handles the apex redirect to www. The www attachment has not been deleted/recreated.

Please inspect the underlying ACME error and Retry-After time, confirm when issuance can safely resume, and reset/reissue the certificate once permitted. Thank you.

Solved

1 Reply

Railway
BOT

a month ago

Your domain's DNS and ownership verification both check out on our side, and the certificate failed only because Let's Encrypt is rate-limiting that hostname after repeated failed attempts, most likely ones made while the record was still mid-move from your previous DNS provider.

With a rate-limit failure, waiting is the only remedy: a fresh attempt made before Let's Encrypt's window clears fails again in the same way, and the error record we hold does not include a specific retry time we can give you. Once the window has passed, a new certificate order can complete now that your records are correct. You don't need to remove and re-add the domain, since that would issue a new CNAME target and verification token.


Status changed to Awaiting User Response Railway • 26 days ago


Railway
BOT

19 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 • 19 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...