Skip to content
Subject: NIMUNU custom domain TXT verification stuck
cosmokamakacci-oss
OP

a month ago

Subject: NIMUNU custom domain TXT verification stuck

Hello Railway Support,

I'm trying to connect www.nimunu.com to my Railway deployment.

My domain is managed through Namecheap, using Namecheap BasicDNS.

The CNAME record is verified successfully, but the TXT verification record is still showing a warning after approximately 48 hours.

I've checked the DNS settings:

  • CNAME: www → nxoz5jf0.up.railway.app
  • TXT Host: _railway-verify.www
  • TXT Value: Copied from Railway
  • TTL: Automatic

Could you please check whether my verification is stuck and, if the public DNS records match, manually re-trigger domain verification and SSL certificate issuance?

I've attached screenshots of my Railway and Namecheap settings.

Thank you!

Solved

1 Reply

Railway
BOT

a month ago

The TXT record at host _railway-verify.www is live, but the value it publishes is cut off partway through the token, so ownership verification can't pass and the certificate can't issue yet. Your CNAME is already correct.

Edit that TXT record in Namecheap so its value is exactly railway-verify=63f14996f4aa94b1710035e8d5e10694c4b4a2ad4deee6b6927b6dc953f3ee16, the full string with nothing trimmed. Once the corrected record propagates, verification and certificate issuance continue on their own, with no re-trigger needed.


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


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...