Custom domain stuck in VALIDATING_OWNERSHIP despite verified DNS + already-issued wildcard cert covering it
i34io
HOBBYOP

a month ago

Issue:

Custom domain api.hugbingsucoffee.com has been stuck in "Validating domain

ownership" (CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP) for 3+ hours, even

though DNS ownership verification succeeded (Verified: yes) from the start.

What I've checked:

  • DNS is clean and correct on multiple public resolvers (1.1.1.1, 8.8.8.8):

    single CNAME api → asuxa716.up.railway.app, single TXT _railway-verify.api

    with the exact expected value, no CAA records, no leftover A records.

  • A wildcard certificate for *.hugbingsucoffee.com was already issued today

    (Google Trust Services, issued 2026-08-22T14:04:01Z, confirmed via public

    CT logs) — it already covers api.hugbingsucoffee.com.

  • TLS handshake on api.hugbingsucoffee.com:443 succeeds, but the server

    presents the generic *.up.railway.app certificate instead of the wildcard

    *.hugbingsucoffee.com cert already issued. This points to an edge

    routing/SNI mapping issue rather than a certificate-issuance problem.

  • I deleted and recreated the custom domain once (new CNAME target

    asuxa716.up.railway.app) — no change, same stuck state.

  • railway domain certificate retry refuses: "Certificate retry is only

    available after certificate issuance fails. Current status:

    CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP."

  • For comparison: the root domain hugbingsucoffee.com (same project, same

    day) verified and got its certificate issued in under a minute.

IDs:

  • Project ID: 70e6359f-7477-49ff-ae16-e586441d7933
  • Service ID (api): 65697235-27cd-4b3f-9cd0-590cd8a6e05a
  • Domain ID (api.hugbingsucoffee.com): aef17e28-1988-4d7b-8248-2a39ae97194a
  • Stuck since: 2026-08-22 15:46 UTC

Could you please check the internal state of this domain and either force

it to re-evaluate, or let me know what's blocking it? Happy to provide more

detail if needed.

Solved

3 Replies

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


a month ago

Your DNS is correct and the domain is verified, but the certificate pipeline stalled after ownership validation passed. We've started a certificate re-issue for this domain, which should complete within a few minutes.


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


brody

Your DNS is correct and the domain is verified, but the certificate pipeline stalled after ownership validation passed. We've started a certificate re-issue for this domain, which should complete within a few minutes.

i34io
HOBBYOP

a month ago

Thanks — but 20+ minutes later, the domain is still stuck in the exact

same state (Verified: yes, Certificate status:

CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP), and api.hugbingsucoffee.com

still returns nothing over HTTPS. The re-issue doesn't seem to have taken

effect. Could you check again?


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


a month ago

The domain is confirmed still stuck in the same state with DNS and verification fully correct. We have kicked off another certificate re-issue now, which should complete within a few minutes.


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


Status changed to Solved i34io • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...