a month ago
My custom domain sharptrace.app on project PolySharp (service: polysharp-production-870b.up.railway.app) has been stuck at "Certificate Authority is validating challenges" for over 40 minutes, across two separate add attempts (I removed and re-added the domain once to force a fresh issuance — same result both times).
DNS is confirmed correct and fully propagated:
TXT _railway-verify.sharptrace.app → railway-verify=6feca486f686a52d044375d4c11171542acec63299a05dc4c4955c1537b2c5e9 (verified via Google's public DNS-over-HTTPS resolver, not just locally)
A records for sharptrace.app → 44.227.65.245, 44.227.76.166 (Railway's edge IPs)
A direct TLS check (openssl s_client -connect sharptrace.app:443 -servername sharptrace.app) shows no certificate at all is being presented for this SNI ("no peer certificate available," handshake failure). For comparison, the sibling domain on the same service (polysharp-production-870b.up.railway.app) presents a valid Let's Encrypt cert (*.up.railway.app) without issue — so the service and networking config are otherwise healthy.
Domain registrar: Porkbun. Can you check why certificate issuance for sharptrace.app isn't completing, or manually trigger a re-issuance?
1 Replies
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
a month ago
Railway only supports CNAME flattening or dynamic ALIAS records for a root domain setup. Porkbun (your DNS provider), doesn't support that. I recommend you change your domain's nameservers to point to Cloudflare's nameservers as a workaround.
You can read more about this here: https://docs.railway.com/networking/domains/working-with-domains#adding-a-root-domain