Skip to content
Custom domain SSL stuck on "Let's Encrypt rate limit reached" (not retryable)
kamranrauf75
OP

24 days ago

Hi, the SSL certificate for our custom domain is stuck in a failed state, and retrying from the CLI is refused.

Project: boattest-brain (5a5ee0e8-c110-46e4-a9dc-f615f22ad63f), workspace BoatTest-AIPA, production

Service: boattest-web

Domain: 360.boattest.com (domain ID 79fc31c9-be34-402c-aff0-321e81a0cbe4)

railway domain certificate retry 360.boattest.com returns: "Certificate retry is not available for this failure. Let's Encrypt rate limit reached. Please wait before retrying." It has returned this every time since 10/23, most recently today, 10/26.

The domain serves the default *.up.railway.app certificate, so browsers show a security warning.

DNS has been correct and verified since 10/23:

CNAME 360.boattest.com → zbewlrch.up.railway.app

The _railway-verify TXT record is in place, and the domain shows ACTIVE

Cloudflare proxy off (DNS only), no CAA records on boattest.com

This looks like a cached failure, not a real Let's Encrypt refusal, like the solved thread "Custom domain SSL stuck on 'Let's Encrypt rate limit reached' (not retryable)":

The domain was created on 10/22 at 11:54 UTC, before its DNS records existed. It shows ISSUE_FAILED and hasn't changed since.

crt.sh shows no certificates issued under boattest.com since September, so we haven't hit Let's Encrypt's weekly limit.

We haven't removed and re-added the domain.

Could someone on the Railway team reset the certificate order for this domain? We launch on Monday 10/26, so a quick fix would help a lot. Thank you!

0 Replies

Status changed to Awaiting Railway Response Railway • 23 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...