Can you send me your DNS configuration and the a screenshot of the custom domain configured on Railway, just so that we can make sure they're both correct

Here you go:

Railway configuration

NameCheap DNS configuration

Awesome, looking good, can you try removing that DNS record and also your custom domain from Railway, then re-add it after? That usually solves issues like this

I've tried that multiple times already with no success :(

https://dnschecker.org/#CNAME/studylouis.com

Based on this DNS checker, it seems that the DNS has successfully propagated, but TLS certificate is taking a long time to issue. Might this be an error on Railway's side?

Also, is it an issue if both my Railway generated domain and custom domain listen on the same port 8080?

No that shouldn't be an issue, I'm not sure what could be wrong here
I do see that you have different nameservers attached though, are you using namecheap as a nameserver?

Yes, I am only using Namecheap as my domain registrar. I also use Resend as my email provider.

Could you help me do a thorough check on what could be causing the issue and ways to rectify it? I'm on a deadline to deploy this project to production by today Appreciate the help!

Based on this DNS checker (https://dnschecker.org/#CNAME/studylouis.com), it seems that the CNAME record has propagated to most regions. What could be hindering Railway from issuing the TLS certificate?

Hey sorry for taking so long to reply, I was asleep
I know you've tried this many times before but can you try one last time, remove everything (the DNS record, the railway domain) then wait a bit and then go through the domain setup process again

I have just done so a few hours back, even re-deploying my entire application, but it's still not working. Please, can I request for an escalation of this issue? If this issue is not resolved, I would have to resort to other hosting providers already. 🙏🏻

By the way, my application is a simple NextJS application that I pushed to Github without any Dockerfile. Is there a need for me to create a Dockerfile, and if yes, is that the reason for the TLS certificate not being issued?

nslookup doesn't even see your domain -

https://www.nslookup.io/domains/studylouis.com/dns-records/#google

If this issue is not resolved, I would have to resort to other hosting providers already.

This is not an issue with Railway, but you should do what you think is best.

This is my CNAME DNS record in Namecheap.

NSLookup shows no DNS records;

but DNSChecker shows some DNS records

@brody how do you suggest I go about debugging and resolving this issue? Thanks 🙏🏻

I don't know what DNS resolver DNSChcker uses, but we use Google's DNS, hence my nslookup link selected to use Google DNS.

We can't help further with DNS issues as that would be far out of our control, instead you would want to get in contact with Namecheap.

Remove the domain from Railway.

Figure out the issue preventing DNS from propagating.

Check the domain with nslookup to see that the correct CNAME is present.

Then finally, you can add the domain back to Railway.

I'm facing the same issue. I don't have much knowledge on dockers and containers and such, I thought it'd be simpler to deploy with Railway than anything else but now am facing weird errors anytime I setup custom domains.

parth, the domain doesn't relate to Docker, and as mentioned, issues with your domain our outside of our control.

The CNAME record is appearing under Control D (unfiltered). I also found out that Namecheap does not use Google DNS. Is this a problem of incompatibility of Namecheap with Railway?

> The CNAME record is appearing under Control D (unfiltered).

Railway uses Google DNS, it is not productive to lookup your domain with anything other than Google's DNS.

> I also found out that Namecheap does not use Google DNS.

No, but Railway uses Google DNS to lookup your domain's records.

> Is this a problem of incompatibility of Namecheap with Railway?

Nope, I use namecheap domains and nameservers with Railway all the time, you have something misconfigured.

I notice that nslookup (Google) now says your domain is pointed to an A record from amazon.