11 days ago
My custom domain has been stuck in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for over 12 hours. The certificate never issues even though DNS is fully correct and Railway itself reports the record as PROPAGATED.
- Domain: www.broker-ifs.com
- Project ID: 793253dc-859a-46d8-aa3c-18367e8172c1
- Service: web-ifs (production)
- Custom domain ID: 9ef762b6-6709-4264-b17b-6e30b846ced5
- Required target: k1n6sxor.up.railway.app
Railway's own API confirms requiredValue == currentValue == k1n6sxor.up.railway.app and status: DNS_RECORD_STATUS_PROPAGATED, yet certificateStatus stays at VALIDATING_OWNERSHIP.
I have verified there is no DNSSEC, the CAA records allow letsencrypt.org, and public DNS (8.8.8.8 / 1.1.1.1) returns a single, stable CNAME to k1n6sxor.up.railway.app. I've already tried deleting and re-adding the domain several times. Could you please manually re-trigger certificate issuance on your side? Thanks.
2 Replies
11 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 11 days ago
11 days ago
You need to add a TXT record for _railway-verify.www.broker-ifs.com. If you are using the API to add your custom domain, you can find it in verificationToken under status.
11 days ago
A Few Questions who are getting your domain from, some providers need a CNAME as well as an ALIAS for the WWW. subdomain.
have you added a TXT record for _railway-verify.www.broker-ifs.com some records require the "." at the end of the url as well
Check CNAME DNS Propagation via https://dnschecker.org/
Check if there are any duplicate A records pointing to an IP address as well sometimes removing that works.