⌘K
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/domains/troubleshooting
Ciadamodavrb 4295 Update on 20 Oct 2026: the same DETRAN-ES phishing is still being deployed on vercel.app, now with new project names. Seen today (the names are in code format on purpose, the pages are live): - `cfcconde.vercel.app` : a driving-school facade whose first lines run location.href to the next one. - `portais-onlines-veiculares-esp.vercel.app` : the fake "Servicos DETRAN-ES Veiculos" page with a plate + Renavam form. Reported on 19 Oct, still online. Its response headers include X-Render-Origin-Server: Render. - `autoescolaauecfc.vercel.app` : a 233-byte page that is only a script redirecting to a gate on another domain. Reports so far: the public abuse form (TNS_01CpK5ull2PyvRp9 on 19 Oct and a new one today) and Pro support cases CSE_01zLc3pGwxWAVDes (closed on 19 Oct with a message that the details were handed to the abuse team) and CSE_01LwnZVYhe3Xxpum (open today). The operator recreates the same pair of projects every few days, so each takedown lasts only until the next deploy. Could someone from Trust & Safety suspend the accounts behind these projects, not only the deployments? Thank you.
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Nielsinc I had the same issue - since I have a Pro account, I was able to ask support. For me, I created a "team/project" scoped token, but creating a full account token fixed it for me: Feedback support bot: During initialization of any CLI command (including `vercel pull`), the Vercel CLI executes an internal preflight check against `GET /v2/user` to load the authenticated user identity. When a Personal Access Token is created with **Team Scope** (scoped strictly to the `specific` team), it is restricted solely to team-level resources and is blocked from accessing the user-level `/v2/user` endpoint. As a result, the preflight check receives a `404 Not Found`, causing the CLI execution to abort before it can pull the project settings. Once the token has account-level scope, the CLI preflight check will succeed and `vercel pull` will successfully retrieve your project configuration and environment variables.
Philkerman 9328 So its basically broken then? If you're allowed to create limited scope tokens but they do a pre-flight that never succeeds, that is broken. The 'fix' to create a wider scoped token just to pass arbitrary pre-flight checks is absolute trash.
