10 days ago
I've been struggling with this for a while now. Off late, Railway's reliability is on a downward spiral.
One of my site was working just fine, then randomly I got a notification to update to the latest NextJS version. I couldn't get to it right away, and when I got a chance to fix it and deploy, I got the SSL certificate error, showed the site being unsecure.
Removed the current custom domain records from both Railway and the DNS provider, and waited for half a day to clear things out. Then added a new custom domain on Railway and added the new entries into my DNS provider. It's been more than 24 hours and it's still stuck at "Validating domain ownership" and no progress since the past 24 hours. I've added both the CNAME and TXT entries it showed me to add.
Don't know what else to do, and there wasn't much help around this on Railway to troubleshoot.
Pinned Solution
10 days ago
Turned out to be a conflicting DNS record on the host side. I added it as a root domain on my DNS provider and after chatting with them I came to know that it was conflicting with some of the existing records. I ended up using the www host name, and it worked. I may move the DNS to Cloudflare at some point, but for now it's too much of a hassle to move those other records as well.
4 Replies
Status changed to Awaiting Railway Response Railway • 10 days ago
10 days ago
I checked with a DNS propagation checker, and I saw mostly green, but there are quite a few reds as well for the CNAME record. Wondering if that has anything to do with this.
Checked the same for the TXT record that Railway asked me to add, I already had a TXT record and that's the one that showed up on the DNS checker, again some green and a bunch of reds.. I checked for the specific one that Railway gave me and everything showed up as red, no green whatsoever at all. This could be the culprit, but not sure why it hasn't propagated yet.
10 days ago
Also, my DNS provider said I can't use the @ record for CNAME as it'd break my mail records and such and advised me to find an alternative record for CNAME. Are there any other options other than the @ record for CNAME?
10 days ago
The solution here is to use a proper DNS provider like cloudflare here is the setup guide, CNAME @ only works on some competent providers.
https://developers.cloudflare.com/dns/zone-setups/full-setup/setup/
10 days ago
Turned out to be a conflicting DNS record on the host side. I added it as a root domain on my DNS provider and after chatting with them I came to know that it was conflicting with some of the existing records. I ended up using the www host name, and it worked. I may move the DNS to Cloudflare at some point, but for now it's too much of a hassle to move those other records as well.
Status changed to Solved noahd • 10 days ago