Custom domain certificates stuck in VALIDATING_OWNERSHIP despite propagated DNS
paul-bennett-ai
HOBBYOP

4 days ago

Subject:

Service: company-statistics (project "statistics", id 32cbbae4-005d-465d-8f15-0873b6119fcb)

Two custom domains are stuck in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP even though the API reports DNS_RECORD_STATUS_PROPAGATED for both:

stats.palmerosco.com (CNAME to sycti41b.up.railway.app, propagated 24+ hours)

oic.palmerosco.com (fresh hostname, CNAME to cgwecqeo.up.railway.app, propagated immediately, still stuck)

Traffic reaches railway-edge on both hostnames over ports 80 and 443 (the edge serves the *.up.railway.app wildcard cert). No CAA or DNSSEC records on the domain. The generated domain company-statistics-production.up.railway.app works fine. Please force certificate issuance or advise. Thanks

$10 Bounty

1 Replies

Railway
BOT

4 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 4 days ago


You need to add a TXT record for _railway-verify.stats.palmerosco.com. If you are using the API to add your custom domain, you can find it in verificationToken under status. Same for _railway-verify.oic.palmerosco.com.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...