2 months ago
The support agent recommended I post here:
Custom domain: www.knollventures.com
Service: knollventures-website-main
CNAME target (current): m13udckn.up.railway.app
All pre-flight checks passed (CNAME correct, no CAA exclusions, no DNSSEC issues, no conflicting DNS records, app healthy, no redirects blocking ACME)
Domain was removed and re-added once (possible Let's Encrypt rate-limit backoff)
Stuck for several hours
Railway support can:
See the actual ACME validation error (you and I can't without account access).
Check if a Let's Encrypt rate limit is in effect and roughly how long until it expires.
Manually re-trigger issuance once any blockers are cleared.
1 Replies
2 months ago
The CNAME record is correct and propagated, but the TXT ownership-verification record is missing, which is why the certificate is stuck. At your registrar, add a TXT record with the name _railway-verify.www and the value shown on the domain's settings page in the Railway dashboard. Once it propagates (usually a few minutes), verification will complete and the certificate will begin issuing.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Solved rfraim • about 2 months ago