a month ago
Title: Custom domain api.receiptmind.co stuck in TXT ownership verification
Hello Railway Support,
My custom backend domain api.receiptmind.co is stuck in ownership/TXT verification even though the DNS records are publicly resolving correctly.
Project: ReceiptMind
Environment: Production
Service: backend
Custom domain: api.receiptmind.co
I have already removed and re-added the custom domain in Railway and recreated the corresponding DNS records in Namecheap.
Public DNS checks through Google DNS (8.8.8.8) now confirm both records resolve correctly.
CNAME:
api.receiptmind.co resolves to the Railway-provided *.up.railway.app target.
TXT verification:
_railway-verif.api.receiptmind.co
resolves to:
railway-verify=04f9c349b2d62af4736b84849925e833da8775cd355c125e9cc5254d8911eb26
The CNAME is recognized, but Railway continues to show the TXT verification as pending.
Could you please check the domain verification state and manually re-trigger ownership verification and/or certificate issuance for api.receiptmind.co?
The Railway-generated backend URL is working normally, so the application itself is healthy.
Thank you.
1 Replies
a month ago
The TXT record is published at a slightly misspelled hostname. The record name is missing the letter "y" at the end of "verify", so it reads _railway-verif instead of _railway-verify. Updating the TXT record's hostname at your registrar to match the exact name shown in your service's Settings under Networking will clear the verification.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 30 days ago