Custom domain stuck in VALIDATING_OWNERSHIP for ~24h despite correct DNS
conradlamyuen
FREEOP

a month ago

My custom domain www.winnersfeed.com has been stuck in

CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for ~13 hours and the TLS cert

never issues.

  • Project: 99472768-7467-4f0f-84fa-e4110739c029, environment production,

    service arcade-app

  • Custom domain id: f7d4e517-8ca3-444b-b4a7-495770657ec3,

    edge target dn8yyn0b.up.railway.app

  • DNS is a correct DNS-only (unproxied) CNAME

    www.winnersfeed.com -> dn8yyn0b.up.railway.app, confirmed PROPAGATED in your

    dashboard. No CAA records, no AAAA records.

  • http://www.winnersfeed.com/.well-known/acme-challenge/ is reachable and

    returns 404 from railway-edge (not redirected), so the HTTP-01 path is not

    blocked.

  • I already deleted + recreated the domain once (with stable DNS) -- it

    re-entered VALIDATING_OWNERSHIP and stuck again. I have NOT recreated since,

    to avoid the Let's Encrypt weekly duplicate-certificate limit.

Can you please check the Let's Encrypt validation error for this domain and

manually re-trigger issuance?

(The app itself is healthy and serving on the temp domain

arcade-app-production-56e5.up.railway.app -- only the www custom-domain cert is

the problem.)

Solved$10 Bounty

Pinned Solution

You need to add a TXT record to _railway-verify.www.winnersfeed.com. You can find the content for the TXT record from the verificationToken property under status.

2 Replies

Railway
BOT

a month ago

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

Status changed to Open Railway about 1 month ago


You need to add a TXT record to _railway-verify.www.winnersfeed.com. You can find the content for the TXT record from the verificationToken property under status.


conradlamyuen
FREEOP

a month ago

Thank you that worked!


Status changed to Solved 0x5b62656e5d about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...