Skip to content
TLS certificate for book.roofingcraftsmen.com stuck on "Let's Encrypt rate limit reached"; retries are refused
jose_escalante
OP

25 days ago

Problem and desired outcome

I added the custom domain book.roofingcraftsmen.com to my service, expecting Railway to issue a TLS certificate automatically. Certificate issuance failed with a Let's Encrypt rate-limit error, and every retry since has been refused with the same error, including after waiting more than an hour. HTTPS on this hostname shows a certificate error, so the domain can't be used. It is still happening. Please check why issuance is blocked and clear it or reissue the certificate.

Resources and timing

  • Workspace: My Projects (8774186a-6dd5-49e8-8ebc-4e2db70d4a9c)
  • Project: rc-booking (f63ee826-be5c-4e14-8f6d-279b00af0bfe)
  • Environment: production (87d8afc4-ddd2-4d55-9663-7577258cc9e6)
  • Service: App Service (21c7497c-b137-4556-aadc-f3228288eb79)
  • Affected domain: book.roofingcraftsmen.com (domain ID 85a8d240-753d-44bb-9197-b72f5134512a), target port 8080
  • Working domain on the same service: book.roofingcraftsmenandsolar.com (domain ID 3792aba5-19fd-4b05-a304-816bca54a76c). Its certificate status is valid.
  • Last observed on 2026-10-26: certificate status CERTIFICATE_STATUS_TYPE_ISSUE_FAILED. I don't have the exact time of the first failure.

Evidence and attempts

Railway domain status, checked several times on 2026-10-26, the same every time:

Verified: yes
Certificate: CERTIFICATE_STATUS_TYPE_ISSUE_FAILED
Certificate error: Let's Encrypt rate limit reached. Please wait before retrying.
DNS_RECORD_TYPE_CNAME book.roofingcraftsmen.com → d3p1df0h.up.railway.app (DNS_RECORD_STATUS_PROPAGATED)

Certificate retries actually performed: three through Railway's retry-certificate API on 2026-10-26, the first more than an hour after the original failure. Each was refused with:

A certificate retry for book.roofingcraftsmen.com cannot succeed yet: Let's Encrypt rate limit reached. Please wait before retrying.

Other checks performed:

  • A public DNS lookup (Google DNS) shows book.roofingcraftsmen.com resolving by CNAME to d3p1df0h.up.railway.app, with no CAA records on that name or on roofingcraftsmen.com.
  • A crt.sh search for unexpired certificates on %.roofingcraftsmen.com returned only two, for roofingcraftsmen.com and www.roofingcraftsmen.com, both issued by Google Trust Services on 2026-08-19. It showed no Let's Encrypt certificates.

I have not removed and re-added the domain, to avoid making more certificate requests.

Why contact support?

The AI assistant recommended contacting support after the retries failed. The retry is refused before reaching Let's Encrypt, and the error says to wait, but waiting more than an hour didn't help. Neither the assistant nor I can see or clear the rate-limit state. Please check which limit is being hit, and clear it or reissue the certificate for this domain.

Uncertainty and constraints

The cause is unknown. One hypothesis is that the limit is on Railway's side, for example its shared Let's Encrypt account or a failed-validation lockout tied to this hostname, rather than the registered domain's weekly certificate limit. That's based on crt.sh showing no unexpired Let's Encrypt certificates for roofingcraftsmen.com. However, crt.sh doesn't record failed validations or expired certificates, so it doesn't rule out a Let's Encrypt limit on this hostname. The other domain on the service works, so I don't want changes to the service or that domain.

Prepared with Railway's support template (v1).

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 25 days ago


dizzydes90
EMPLOYEE

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...