Custom domain stuck in VALIDATING_OWNERSHIP for 10+ hours across multiple delete/recreate attempts
plaidwaresolutions
HOBBYOP

8 days ago

Custom domain hub-staging.plaidware.com on service hub-web (project id 3722099f-6952-4b74-af95-42a14168f4e5, environment staging) has been stuck in VALIDATING_OWNERSHIP for 10+ hours across multiple delete/recreate attempts. The CNAME (hub-staging.plaidware.com → 6nyzbi2p.up.railway.app) shows DNS_RECORD_STATUS_PROPAGATED in your API, the record is not proxied, and the zone has no CAA or DNSSEC records. Certificate issuance never completes. Please investigate cert issuance for this domain.

Solved

2 Replies

Railway
BOT

8 days ago

The domain's CNAME record is correctly propagated, but the TXT ownership-verification record is missing. Custom domains need both a CNAME for routing and a TXT record for ownership verification before a certificate will issue. In your DNS provider, add a TXT record on the host _railway-verify.hub-staging (under your plaidware.com zone) with the verification value shown on the domain's settings page in the Railway dashboard, then certificate issuance should proceed once it propagates.


Status changed to Awaiting User Response Railway 8 days ago


plaidwaresolutions
HOBBYOP

5 days ago

thanks, that solved it.


Status changed to Awaiting Railway Response Railway 5 days ago


Status changed to Solved mayori 5 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...