Skip to content
Custom domains stuck in "Validating ownership" for ~19 hours, DNS records are correct
Anonymous
OP

a month ago

Hello Railway team,

My two custom domains have been stuck in ownership validation for about 19 hours, and no certificate has been issued. Visitors get ERR_CERT_COMMON_NAME_INVALID, because the edge serves the default *.up.railway.app certificate.

Project / service

  • Project ID: 7f1231e0-64da-4b24-8aaa-adf194e00dce
  • Service: lecturehelper, environment: production
  • Domains:
    • lecturehelper.com, domain ID 049c66ef-f298-4047-ae5c-781f3ad9aa12, target port 8080
    • www.lecturehelper.com, domain ID 6ded5348-1dd3-404b-8bb9-2328c50935fc, target port 8080

Current status (railway domain status)

  • DNS record status: PROPAGATED for both
  • verification.verified: false for both
  • certificate.status: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for both

DNS (Namecheap BasicDNS), correct since 2026-10-19 ~19:30 UTC

  • ALIAS @ -> xe078t82.up.railway.app (resolves to 69.46.46.123, same as the target)
  • TXT _railway-verify -> railway-verify=6fc0c415e5acb9fb9d61b4bd52ffe1ff7fd3a00c1f3016202e043e29be10a608
  • CNAME www -> 024e9rae.up.railway.app
  • TXT _railway-verify.www -> railway-verify=a81185fdb148b433595d136976cdc50cdb04c87bfb1eea12fe6d05484c379e47

All four records resolve correctly on Google (8.8.8.8) and Cloudflare (1.1.1.1) DNS-over-HTTPS.

Other checks

  • No CAA records on lecturehelper.com. The www CNAME chain leads to railway.app, whose CAA allows letsencrypt.org.
  • DNSSEC is not enabled (no DS record at .com, no DNSKEY).
  • "railway domain certificate retry" returns: "Certificate retry is only available after certificate issuance fails. Current status: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP."

Timeline (UTC)

  • 2026-10-16: domains added in Railway. My first DNS edits did not save, so for a while only the registrar's parking records existed.
  • 2026-10-19 ~19:30: correct records saved. Railway marked them PROPAGATED shortly after.
  • 2026-10-20 14:55: still VALIDATING_OWNERSHIP.

My guess is that ownership validation started while the parking records were still in place and was never re-checked. Could you please re-trigger ownership validation and certificate issuance for both domains? Please don't remove the domains, so the DNS values stay the same.

Thank you!

Solved

1 Reply

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


a month ago

Hey! Try removing the domain from your service and the records from your DNS, wait 15-20 mins and re-add it.


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


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


Railway
BOT

24 days 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 • 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...