a month ago
-
I cannot access my website using my custom domain.
-
Railway link and deployment shows success. However, at every deployment, I receive and email saying it crashed.
Pinned Solution
a month ago
Railway will automatically validate the DNS and issue certificates within a few hours (maybe up to a day). If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
Also, your CNAME should be the one Railway provided for you when you added the domain. It shouldn't be the Railway-generated URL for your service.
7 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 28 days ago
a month ago
If your deployment is showing “success,” I’d try adding a custom deploy command in youe service settings. It should be showing “online” instead. If that doesn’t work, I’d try using a Dockerfile or a custom Railpack configuration.
a month ago
Thanks for the suggestion. My deployment is already online and working fine on the Railway domain. The issue is specifically with custom domain provisioning — both my DNS records (TXT verification and CNAME) are live and resolving correctly, but Railway still returns 'Not Found' when accessing the website. This isn't a build or deployment config issue. Can you escalate this to the infrastructure/networking team to investigate the domain provisioning?"
a month ago
Can you share the domain you're trying to add? A "Not Found" usually means the verification went wrong.
a month ago
I couldn't find a TXT record on _railway-verify.www.litreviews.ai. Make sure you've added it to the correct target.
a month ago
TXT record at _railway-verify.www.litreviews.ai is live
CNAME resolves correctly to litreviews-mvp.up.railway.app
Still getting "Not Found"
Request ID ubBakCIBTUSIE0Lf21mRUA
a month ago
Railway will automatically validate the DNS and issue certificates within a few hours (maybe up to a day). If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
Also, your CNAME should be the one Railway provided for you when you added the domain. It shouldn't be the Railway-generated URL for your service.
Status changed to Solved 0x5b62656e5d • 27 days ago