BOM1 routing entry is missing for www.samishacouture.com. I’ve confirmed DNS, SSL, deployment, and domain config are all correct on my end. Please fix the routing propagation to BOM1.
It looks like you’re seeing a 404 issue instead, can you review the following?
i need more help i debugged everything please check
Hi Pauline, here’s the exact error I’m seeing:
404: NOT_FOUND
Code: DEPLOYMENT_NOT_FOUND
ID: iad1::2kpz8-1722542758508-701865fa4a7a
It says “This deployment cannot be found” — so it seems like www.samishacouture.com is still routing to an old deleted deployment rather than my current active one. I mentioned the BOM1 routing entry earlier which may be related.
Could you please reassign the domain to my latest active deployment, or advise how I can do this from my dashboard? The domain config, DNS and SSL all show as correct on my end.
Hey, @samishacouture-9932! Did you take a look at the guide we shared above? ![]()
This isn’t a domain, DNS, SSL issue or with the BOM1 routing AFAIK. From the guide:
It’s a good idea to check the deployment URL for typos or incorrect paths. This is especially true when accessing specific deployments using Generated URLs which contain a unique hash.
You should review the deployment list from your project dashboard to make sure that (1) the deployment was successful, (2) the deployment was not deleted, and (3) the URL you’re visiting is the correct one for that deployment.
If the deployment exists, review the deployment logs for issues that might have caused the deployment to be unavailable. If there are uncaught errors in a function or component, those could bubble up and cause you to see a 404 error. In this case a try/catch statement can help.
If the deployment exists, can you make sure your domain is pointing to the right one?
Hi Pauline, I’ve followed every step in every guide you’ve sent and my site is still down. DNS is correct, deployment is green, env vars are set — everything on my end is done.
The error is DEPLOYMENT_NOT_FOUND on BOM1 which is a Vercel infrastructure issue, not something I can resolve from my dashboard. I’ve been going back and forth on this for over 2 days now.
Could someone from the engineering team please take a look directly? I’d really appreciate a proper fix rather than more guides to follow. Thank you.
@samishacouture-9932 Did you end up fixing it? It looks like www.samishacouture.com is live now ![]()
From the limited logs I see you ended up linking the deployment to the domain, is that right?
It wasn’t a infrastructure issue.
