a month ago
Custom domain bbvotetelugu.com stuck in VALIDATING_OWNERSHIP for hours.
DNS propagated:
CNAME → vqo90qqo.up.railway.app
TXT → railway-verify=cf9e147fe22cbf53416e58e5178de05db08e835df8579d356e183d5553235eef
HTTPS still wrong cert (*.up.railway.app). Please re-issue cert / unstick verification.
Project 8254abc9-a34f-44a6-b026-c5d2fe6dfe34 · Service 27290f18-359c-452e-b63b-ecf7cd23c3bc · Env 862d96c9-a041-4fd1-824b-0e7d88cb679e · Domain 6bbb8f5c-b2f8-49a6-81e4-2d1aa9c81822
Working URL: https://bb-vote-telugu-production.up.railway.app
Other options: wait longer, or upgrade to Pro only if you want private support — upgrading alone won’t fix SSL.
1 Replies
a month ago
Your CNAME is correct and propagated, but the TXT verification record is on the wrong host. It's currently published on the root domain instead of at _railway-verify. At your registrar, create a TXT record with host/name _railway-verify and the same verification value you already have, then remove the TXT from the root. Verification and certificate issuance will resume automatically once the corrected record propagates.
Status changed to Awaiting User Response Railway • about 1 month ago
23 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 • 23 days ago