Hey, Railway has most likely already given up on checking for DNS updates if your domain in question wasn't set up properly and then set up properly after a while. Please readd your domain and add the required CNAME record in a timely manner and see if this fixes the issue.

I can access my site, but I get warning regarding invalid certificate... How do I sort this?
My site is down for about 48hrs now

Can you try following the Custom Domains guide on our docs? (https://docs.railway.com/guides/public-networking#custom-domains)

Some extra info needed: Is your site working or not? You said you can access it but it's been down for the last 48 hours
And what is your domain provider?

Namecheap, I can access it via the domain but my browsers warns for invalid certificate, but I proceeded anyway.
On railway dash, It's still waiting for updates...

Someone help me, DNS verification stuck at "issuing TLS certificate"

Hey, have you tried removing the custom domain and readding it as I have suggested?

yea, I did

If your domain shows up but you're still getting the invalid cert warning, and Railway's stuck on "waiting for updates", it probably gave up checking after the first DNS fail.

That tends to happen when the domain gets added before the CNAME is fully set — even if you fix it later, it doesn’t always trigger a retry.

What usually works is: remove the domain, give it a minute, then add it back once you're sure the CNAME is in place and resolving.

Quick way to confirm is to throw it into dnschecker.org and make sure it shows up.

Once it sees the record during the add step, TLS should go through cleanly.

This is a bit frustrating right now, I reached out to my domain provider and they they asked me to reach out to my hosting provider. Any insider here to help check this out. I'm tired of this back and forth!

Can you please share the domain? I will check it out for you.

turningauto.app

I believe the problem is that you have a CNAME record set on your root domain.
turningauto.app. 1723 IN CNAME 6rchm0s9.up.railway.app.

Please change it to an A record.

It doesn't accept an A record, I have to give it an IP address if A record is given

could it be that in the domain setting there are more than just the one cname? check if you have any A records pointing towards the landing page of your registar some registar like to do that so they have a landing page for domains without websites, the oens you should have are mx records only if you are using a email also all associated records for verifying the emails like SPF, DKIM, and DMARC, so try to remove everything and only point to the cname to the one from railway

Can you try using Cloudflare? It will not just be useful for your project but also solve this problem.