a month ago
"Custom domain bestpractices.wetransact.io on project 74f93abd-ea3b-4be0-83ea-4318f0ff5be0, service web — SSL certificate stuck on VALIDATING_OWNERSHIP for 12+ hours. DNS CNAME correctly points to cfgmdtp5.up.railway.app, fully propagated. Please re-trigger cert issuance."
Pinned Solution
a month ago
You need to add the TXT record as instructed by the popup when adding your custom domain in your Railway dashboard.
3 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Open Railway • about 1 month ago
a month ago
You need to add the TXT record as instructed by the popup when adding your custom domain in your Railway dashboard.
a month ago
"The TXT record _railway-verify.bestpractices has been added to our Azure DNS with the exact value Railway expects (railway-verify=a7fb0aecb2a68469298a9cc37b272d8c32cb0562de4044041b74a753f2abb5ca). Confirmed propagated on Google DNS and Cloudflare DNS. However, the custom domain still shows Verified: false and cert status VALIDATING_OWNERSHIP. Can you trigger a manual re-verification on your side? Domain ID is 37e90765-c7fb-4ce3-9902-381329789b4c."
a month ago
If it doesn't validate within the hour, I'd try removing the domain from Railway and Azure, waiting for ~10-15 mins, then adding them back.
Status changed to Solved 0x5b62656e5d • 4 days ago