14 days ago
• CNAME record for @ and www point to the exact target Railway provided (currently ur3rv8mt.up.railway.app)
• TXT verification record (railway-verify=a581c36a2196972a72e994462effcca596a8726a13fa31007090ec44f7ce47a1) is set correctly on @
• Both CNAME records are set to DNS only (grey cloud, proxy disabled) in Cloudflare, not proxied
• I’ve already tried removing the domain, waiting 15 minutes, and re-adding it — the issue persists with the new CNAME target
• The default Railway domain (bigchains-backend-production.up.railway.app) works perfectly and serves the app correctlyCould you please manually check the DNS verification status on your end, or re-trigger it? DNS is confirmed propagated correctly via multiple public resolvers.
Thank you.
1 Replies
14 days ago
The TXT verification record is currently published on @ (the root), but it needs to be a separate record on the host _railway-verify. In Cloudflare, create a new TXT record with the name _railway-verify and the value railway-verify=a581c36a2196972a72e994462effcca596a8726a13fa31007090ec44f7ce47a1, then remove the verification entry you placed on @. Your CNAME is resolving correctly to our edge already. Once the corrected TXT record propagates, verification and certificate issuance will resume automatically with no need to remove or re-add the domain.
Status changed to Awaiting User Response Railway • 14 days ago
7 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 • 7 days ago