7 days ago
My custom domain www.ringcaptain.com has been stuck in certificateStatus VALIDATING_OWNERSHIP for 6+ hours; the Let's Encrypt cert never issues, so HTTPS never works and Railway won't route the host.
Project: ring-captain (id b79116ad-6ae1-4ea5-89bd-39081ca900c6), environment production
Service: ring-captain (id 1cf221c3-fad0-46c8-93b1-b31d87185792)
Custom domain: www.ringcaptain.com (id e4efa213-1867-4ef2-ba28-d943df0ae216), target 8ffr4qu6.up.railway.app
Verified on my side:
- DNS is a DNS-only (unproxied) Cloudflare CNAME www.ringcaptain.com -> 8ffr4qu6.up.railway.app
-
- Railway's domain status reports the DNS record PROPAGATED with currentValue == requiredValue
-
- No CAA records on the zone
-
- ACME challenge path http://www.ringcaptain.com/.well-known/acme-challenge/ is reachable (404, not a redirect); http root returns Railway's 301 to https
-
- Only one custom domain on the service (no orphans)
-
- Early on I deleted/re-added the domain a few times, then stopped and left it untouched
DNS resolves and HTTP routing (301) works -- only the certificate never finishes validating. Could you please force a certificate re-issue / re-trigger ownership validation for www.ringcaptain.com? Other users appear to be reporting similar custom-domain/cert stalls today. Thank you!
Pinned Solution
7 days ago
You need to add a TXT record for _railway-verify.www.ringcaptain.com. If you are using the API to add your custom domain, you can find it in verificationToken under status.
1 Replies
7 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 7 days ago
7 days ago
You need to add a TXT record for _railway-verify.www.ringcaptain.com. If you are using the API to add your custom domain, you can find it in verificationToken under status.
Status changed to Solved 0x5b62656e5d • 7 days ago