Skip to content
Custom domain stuck in VALIDATING_OWNERSHIP ~24h — DNS verified correct, all documented causes ruled out
Anonymous
OP

4 months ago

▎ My custom domain breakoutresearch.io (project e86ddf9d-8fb1-4e20-bde0-2151fd0200d4, service "web") has been stuck in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for ~24 hours across multiple delete/re-create cycles.

▎

▎ Verified: your API reports DNS_RECORD_STATUS_PROPAGATED; the ALIAS record resolves globally to your edge (matches the assigned target exactly); port 80 and 443 both route to Railway (your edge serves the *.up.railway.app wildcard for my hostname); no CAA records; no DNSSEC; no Cloudflare proxy (DNS-only at Porkbun); crt.sh shows zero issuance attempts completing. A www subdomain with a clean CNAME (your checker reads the correct currentValue) exhibits identical behavior, so this isn't apex/ALIAS-related. Can you check the certificate issuance job for this domain?

Solved$10 Bounty

Pinned Solution

You need to get the TXT record through the verificationToken property under status if you’re using the API.

2 Replies

Railway
BOT

4 months ago

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

Status changed to Open Railway • 4 months ago


Status changed to Solved Anonymous • 4 months ago


Anonymous
OP

4 months ago

the API's dnsRecords response omits the required _railway-verify TXT record — it's only shown in the dashboard UI. Adding the TXT record issued the cert in under a minute."


Status changed to Awaiting Railway Response Railway • 4 months ago


Status changed to Open 0x5b62656e5d • 4 months ago


You need to get the TXT record through the verificationToken property under status if you’re using the API.


Status changed to Solved 0x5b62656e5d • 27 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...