Custom domain stuck in VALIDATING_OWNERSHIP for 3+ hours
arturarruda-neo
HOBBYOP

a month ago

My custom domain www.no-topo.com has been stuck in

CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for over 3 hours.

Project: no-topo (3be9ae25-c6bd-4e7f-a437-98e767865abf)

Service: notopo (d9f50949-170d-4f94-8020-f7cbb15566bf)

Custom domain ID: 732b106a-c51d-4cca-b559-b728c8fdeebe

Target: 25pwuv4f.up.railway.app

What I have verified on my side:

  • DNS is correct and propagated. Railway's own API reports

    currentValue == requiredValue and DNS_RECORD_STATUS_PROPAGATED.

  • The CNAME is NOT proxied by Cloudflare (grey cloud), so it resolves

    straight to Railway.

  • There are no CAA records on the zone (checked apex and www).

  • Railway's edge already recognizes the host: an HTTP request to

    http://www.no-topo.com/ returns 301 with the x-railway-* header, and

    /.well-known/acme-challenge/ returns 404 instead of redirecting,

    which suggests the ACME challenge path is being handled but the

    certificate is never issued.

  • Port 443 refuses the TLS handshake, as expected while no certificate exists.

  • I previously tried the apex (no-topo.com) and it also never validated,

    so I deleted it and created www instead. The www domain was also

    recreated once, which did not help.

Could you check why certificate issuance is not completing for this domain?

Solved

1 Replies

Railway
BOT

a month ago

The CNAME record is correctly propagated, but the TXT ownership-verification record is missing. Railway custom domains require both a CNAME (for traffic routing) and a TXT record (for ownership verification) - the certificate will not issue until the TXT record is in place and verified. The verification token and the host to publish it at are shown alongside the domain in your service's networking settings (or via the API's verificationToken field, which is returned separately from dnsRecords). Add that TXT record at your DNS provider, and once it propagates the domain should verify and the certificate will follow.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...