Custom domain cert stuck at VALIDATING_OWNERSHIP — domain verified, port set, TXT resolves
drub
HOBBYOP

3 months ago

Custom domain demo.con-tatto.app has been in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for

approximately 3 hours with no progress.

Project: magnificent-peace

Service: clubdir

Domain ID: f8bce652-7cac-415e-a7b6-c7aab69ae962

DNS is correct and resolves:

  • CNAME: demo.con-tatto.app → vgnzfofc.up.railway.app ✓
  • TXT: _railway-verify.demo.con-tatto.app →

railway-verify=68e1fb3a172ce39c1ab1e684ee4bee53aeddb035b8218249753635da4cc12978 ✓ (confirmed

via dig TXT _railway-verify.demo.con-tatto.app +short)

Steps taken:

  • Domain was originally added 2026-06-21 with no target port set (blank)
  • Port updated to 8080 today via railway domain update demo.con-tatto.app --port 8080
  • railway domain certificate retry returns: "retry only available after certificate issuance

fails" — status never advances to failed

Current CLI status shows Verified: no and Sync status: ACTIVE. The wildcard *.up.railway.app

cert is being served. No change in status for 3+ hours despite correct DNS.

Can you check whether ownership validation is stuck on your end and manually trigger a retry?

Solved$10 Bounty

Pinned Solution

If a certificate isn't issued by Railway within a day, try to remove your custom domain and all its related DNS records, wait for 10 - 15 minutes, and add it again.

2 Replies

Railway
BOT

3 months ago

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

Status changed to Open Railway • 3 months ago


If a certificate isn't issued by Railway within a day, try to remove your custom domain and all its related DNS records, wait for 10 - 15 minutes, and add it again.


darseen

If a certificate isn't issued by Railway within a day, try to remove your custom domain and all its related DNS records, wait for 10 - 15 minutes, and add it again.

drub
HOBBYOP

3 months ago

Many thanks!


Status changed to Solved uxuz • 3 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...