23 days ago
I purchased the domain koursekit.com through Railway and linked it to my frontend service (target port 3000). Railway repeatedly fails to issue a TLS certificate for the custom domain.
Steps that occurred:
- Added
koursekit.comas a custom domain in Railway - Railway began the cert provisioning process: "Generating private key" → "Setting up challenge responses" → "Certificate Authority is validating challenges" → "Fetching issued certificate"
- Each attempt ends with: "Failed to issue TLS certificate"
- After several retries, now hitting: "Let's Encrypt rate limit reached. Please wait before retrying. This error cannot be automatically retried."
Error messages seen:
Failed to issue TLS certificateLet's Encrypt rate limit reached. Please wait before retrying.- Browser:
net::ERR_CERT_COMMON_NAME_INVALID
Notes:
- DNS is resolving correctly —
koursekit.comCNAMEs to6njprd86.up.railway.app→151.101.2.15 - No CAA records blocking Let's Encrypt
- The domain was purchased through Railway itself
GitHub repo:https://github.com/Amr-El-Masri/KourseKit
Pinned Solution
23 days ago
Unfortunately you'd need to wait until next week for the limit to reset. This may have been a result of Railway attempting to issue certificates during Fastly's incident yesterday.
There isn't anything Railway can do about the rate limit.
1 Replies
Status changed to Open Railway • 23 days ago
23 days ago
Unfortunately you'd need to wait until next week for the limit to reset. This may have been a result of Railway attempting to issue certificates during Fastly's incident yesterday.
There isn't anything Railway can do about the rate limit.
Status changed to Solved 0x5b62656e5d • 9 days ago