a month ago
Two custom domains on my service have stayed "Pending" and no certificate has been issued. HTTPS on both still presents the default certificate (CN=*.up.railway.app, Let's Encrypt YE2), so browsers reject them with a name mismatch.
Project: refreshing-wonder (production), deployed from GitHub
Railway domain (works): oversoundai-production.up.railway.app
Custom domains:
- live.oversound.ai
- oversound.ai
DNS is at Cloudflare, DNS only (grey cloud, not proxied). Checked from 1.1.1.1, 8.8.8.8, 9.9.9.9 and OpenDNS; all agree:
- NS oversound.ai: joselyn.ns.cloudflare.com, stan.ns.cloudflare.com (the .ai registry delegation is updated)
- CNAME live.oversound.ai -> dn74zz70.up.railway.app
- TXT _railway-verify.live.oversound.ai: present, as given by Railway
- TXT _railway-verify.oversound.ai: present, as given by Railway
- oversound.ai (apex): the record Railway gave, flattened by Cloudflare; resolves to 69.46.46.96
- live.oversound.ai resolves to 69.46.46.28 (Railway, not Cloudflare)
- No CAA records on oversound.ai or live.oversound.ai
What we see:
- http://live.oversound.ai -> 301 to https (so the request reaches Railway)
- https://live.oversound.ai and https://oversound.ai -> the *.up.railway.app certificate
The domain was registered on 2026-10-25 (01:58 UTC) at GoDaddy and moved to Cloudflare nameservers shortly after.
Could you re-trigger verification and certificate issuance for these two domains, or tell me what is blocking them? Thank you.
1 Reply
Status changed to Awaiting Railway Response Railway • 27 days ago
a month ago
Same here since the 21 Oct incident: a brand-new custom domain failed its very first certificate attempt with “Let’s Encrypt rate limit reached … cannot be automatically retried”. DNS is verified on Railway’s side, there’s no CAA, and no certificate was ever issued for the name. A domain in the same zone got its certificate on 16 Oct, before the incident. That looks like a platform-side issue rather than DNS. +1 for a staff look.
Status changed to Awaiting Railway Response Railway • 27 days ago
Status changed to Awaiting User Response Railway • 27 days ago
20 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 20 days ago