2 months ago
I'm setting up a custom domain for my railway project and it's been stuck in the "Validating domain ownership" step for quite some time.
I've confirmed that both CNAME and TXT DNS records are configured correctly, and per similar threads have tried removing and re-adding the custom domain.
Seeing a lot of similar threads pop up recently so wondering if this is an issue on Railway's side.
4 Replies
2 months ago
Your DNS records for www.kudos-bot.com are correctly configured and ownership verification has passed, but our systems are detecting a stale CNAME target from a previous configuration, which is likely why the certificate is stuck in the validating state. Please try removing the custom domain from your service and re-adding it so a fresh CNAME target is issued, then update your DNS CNAME record to match the new target shown in the dashboard.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
For additional context, this thread had a similar bot response: https://station.railway.com/questions/validating-domain-ownership-82d498c0
As recommended I've removed and re-added the custom domain twice, none of which resulted in an update.
2 months ago
Hey,
Sorry about that. We have rolled out a fix for this. Your domains should automatically get issued a certificate. If they don't, please remove and re-add the domain.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
Seeing this is fixed, thanks!
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved cschlaepfer • about 2 months ago