Custom domain returning DEPLOYMENT_NOT_FOUND (worked previously on Vercel, now migrated to Railway)

Hi Railway team ,

I’m facing an issue with a custom domain setup and would appreciate any guidance.

Situation:

  • I previously used my domain happychild.in on Vercel.
  • I completely deleted the Vercel project and removed the domain from Vercel.
  • Now I have fully migrated the project to Railway.

Current status:

  • My Railway default URL works perfectly and www.happychild.in: https://backend-production-0d93.up.railway.app www.happychild.in
  • But when I open: https://happychild.in I get: 404: DEPLOYMENT_NOT_FOUND

DNS Setup:

I’m using Cloudflare and I’ve configured:

I already:

  • Deleted old Hostinger nameservers
  • Purged Cloudflare cache
  • Re-added domain inside Railway → Settings → Domains

Railway now shows Setup complete, but the domain still throws DEPLOYMENT_NOT_FOUND.

Suspicion:

It feels like the domain might still be cached/associated somewhere from the old Vercel deployment, or Cloudflare is holding old routing.

Question:

Is there any internal Railway step required to “force refresh” or reattach a domain that was previously used on another platform?

Any help from the team or community would be greatly appreciated

Solved

2 Replies

Railway
BOT

6 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


Status changed to Solved cypherninjaa 6 months ago


i resolve this by flushing dns records

Attachments


Status changed to Awaiting Railway Response Railway 6 months ago


Status changed to Solved cypherninjaa 6 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...