Custom domain SSL certificate stuck: Let's Encrypt rate limit confirmation needed
onyraapp
FREEOP

a month ago

I'm requesting confirmation of my domain's certificate request state and the exact date/time when the Let's Encrypt rate-limit window closes.

Domain: api.beachdayindex.com

Project: powerful-dream

Service: beach-day-index-platform

What happened: On July 10, 2026 (GMT+2), I attempted to connect this custom domain to the service. The SSL certificate became stuck on "Waiting for DNS update" despite:

CNAME record correctly pointing to Railway's target

TXT verification record matching exactly what Railway's panel displays

DNS verified as propagated via dig against both 8.8.8.8 and 1.1.1.1

To troubleshoot, I removed and re-added the custom domain multiple times over several hours. Each time, Railway generated a new CNAME target, which I immediately updated in my DNS provider (Namecheap), and DNS propagated correctly each time. However, the certificate never issued.

I've since identified this was likely caused by Let's Encrypt's rate limit of 5 duplicate certificates per domain per week. The repeated remove/re-add cycles likely consumed those 5 attempts and triggered the 7-day issuance block.

Current state: The domain is now added to the service and I will not remove it again.

What I need:

Confirmation of the exact date and time when certificate issuance becomes available again for api.beachdayindex.com

Confirmation that no further action is needed on my end beyond waiting out the rate-limit window

(Optional) Confirmation of how many certificate request attempts were made for this domain on July 10, 2026

Thank you.

Solved$10 Bounty

Pinned Solution

The rate limit is based on a 7 day window. Also, your TXT record is incorrect. It should start with railway-verify=. Make sure to copy exactly what Railway provided.

1 Replies

Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway about 1 month ago


The rate limit is based on a 7 day window. Also, your TXT record is incorrect. It should start with railway-verify=. Make sure to copy exactly what Railway provided.


Status changed to Solved 0x5b62656e5d 7 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...