Project: translucid-studio (scope chrishakimofficial-2304s-projects) Production deployment: dpl_FHmg9qeQ26RSpoVsWfh4Rk9iJ7b8
Every production hostname for this project returns HTTP 404 with a zero-byte body and no content-type header, on every path including /. This is the platform’s “no deployment for this host” response, not my application’s 404 page, which would return HTML.
Affected: translucid.studio, www.translucid.studio, and translucid-studio.vercel.app.
What I have verified:
The deployment is ● Ready, target: production, built 2026-07-30, and vercel inspect lists all five aliases attached to it, including the three above. Its build output includes the expected routes (λ index, λ about, etc). The .vercel.app domain fails identically, so this is not DNS. Vercel’s dashboard shows it as Valid Configuration. Requesting the raw deployment URL translucid-studio-jjuymh1in-…vercel.app returns 302 to vercel.com/sso-api, i.e. the deployment itself responds and is behind Deployment Protection. So the build is serving; only the aliases 404. I re-ran vercel alias set for the apex. It reported success and the behaviour did not change. DNS is correct and verified: apex A 76.76.21.21, no AAAA, www CNAME cname.vercel-dns.com, all DNS-only (unproxied). Both domains show verified in the dashboard with only the soft “DNS Change Recommended” notice. A valid Let’s Encrypt certificate for translucid.studio was issued 2026-07-30 19:32 UTC, so Vercel is terminating TLS for the host. There is no paused, disabled, or over-limit banner anywhere in the dashboard, and no warning on the Usage page. A representative failing request: x-vercel-id: sin1::2jp55-1785451809362-e57f371cf74b.
So: cert issued, host verified, alias assigned, deployment Ready, and the edge still has no deployment mapped for these hostnames. Please check the routing/alias records for this project server-side.
Update: I have now done all three suggested steps. Deployment target confirmed production via vercel inspect. Framework preset is set explicitly in vercel.json ("framework": "nextjs", no output override) and the build manifest contains λ functions for every route. I triggered a fresh production deployment (dpl_Ap1qik17vJgSQ9cz7KtWuGhJ4E2R, Ready, all aliases attached) and the behaviour is unchanged: translucid.studio, www.translucid.studio and translucid-studio.vercel.app all return HTTP 404 with a zero-byte body and no content-type.
Note that translucid-studio.vercel.app fails identically, which excludes DNS and my own domain entirely, and the dashboard marks it Valid Configuration. Two separate production deployments, seven hours apart, both Ready with aliases correctly bound, both unreachable. This looks like a stale server-side alias or routing manifest that redeployment is not clearing.