3 months ago
I have two custom domains (a frontend service and an api service) whose Let's Encrypt certificate won't issue. Railway's own status shows the CNAME as PROPAGATED with requiredValue == currentValue, there's no CAA record, and the ACME HTTP path returns 404 from the Railway edge — yet certificateStatus has stayed VALIDATING_OWNERSHIP for hours with 0 certs issued. Looks like a stuck ACME order or a Let's Encrypt rate-limit.
Pinned Solution
3 months ago
Make sure you added the TXT record at _railway-verify.<DOMAIN> where <DOMAIN> is the domain you're trying to add. You can find the content for it from the verificationToken property under status.
1 Replies
3 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 3 months ago
3 months ago
Make sure you added the TXT record at _railway-verify.<DOMAIN> where <DOMAIN> is the domain you're trying to add. You can find the content for it from the verificationToken property under status.
Status changed to Solved 3lsaya • 3 months ago