⌘K
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. 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.
galb Same request here, from Lookout (lookoutstats.com), a cross-project dashboard for Vercel Web Analytics. We see exactly what you describe: our integration token gets 200 on /v10/projects but 404 "Web Analytics not found." on every /v1/query/web-analytics/visits/* query, and the App permissions editor offers only OpenID scopes. Support also sent us to Community rather than opening a case. We'd like the same two private-beta permissions for our Sign in with Vercel app: Web Analytics: Read Only and Projects: Read Only. Today our users have to paste a personal access token, which is worse for their
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. vercel.com/docs/domains/troubleshooting
sam We need authoritative guidance for one files-based Preview deployment in an existing Vercel project. Required invariants: Every existing configured, branch, member, and custom-domain alias must retain its current deployment throughout creation. The new deployment must have only its immutable deployment URL and zero aliases. No Production deployment or project-setting change is authorized. CLI 62.1.0 documents --skip-domain as Production-only. Is there a supported CLI, REST API, or project control that prevents all automatic alias assignment for Preview? Please specify the exact supported param
Amy Egan As you already saw in the documentation, --skip-domain is used with the --prod option. Branch deployments get their own branch domain that is automatically updated to the latest deployment from that branch. Each deployment also gets a unique URL. The unique deployment URL stays with that deployment, and a new one is assigned to the next deployment. If you need a fixed domain then I'd recommend using the unique generated URL. If you can explain more about the bigger picture for your situation, I might have some other ideas about how to accomplish what you need.
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. 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.
Chrisrivero Dev Hey, This doesn’t sound like a 404 issue. If the function is hanging for about 60 seconds and then dying with INTERNAL_FUNCTION_INVOCATION_FAILED, I’d first try to confirm whether the function is actually entering your handler in Vercel. Can you add a log as the very first line of the function and see if that appears in the invocation logs? If it does, then I’d start checking what it’s waiting on after that, especially a database connection or anything environment-specific between local and Vercel. If the first log never appears, that points more toward the runtime/startup side rather than you
Jacob Paris This is an initialization timeout, failing before your server receives its request. The most likely reason is if server.listen() never completes in a way that Vercel can see For zero-config Node servers, Vercel captures your server.listen() call while the module loads and routes traffic to it internally, ignoring the PORT you pass. This removes a layer of overhead by letting Vercel serve your server directly instead of receiving and passing into an internal service. Running the built server.mjs directly with Node skips that step, which is why it works locally. I think it's possible that passin
Amy Egan Thanks for reporting this. I'm checking with the team about it
Romlenzotti Hi @amyegan Thanks for your message. On the example I finally fixed the problem. { "$schema": "openapi.vercel.sh/vercel.json", "bunVersion": "1.4.x", "framework": "bun" // this line is required, but missing in the example } But in the vercel backoffice Bun framework is missing. This is why I haven't tried that, and in my mind bunVersion should trigger bun automatically. After that I faced to another issue. One the dependencies (universal-github-app-jwt) of octokit to consume github API use internal imports to resolve crypto lib depending on the : { "imports": { "#crypto": { "node": "./lib/cryp
Amy Egan Glad you got it working! I'll add these notes to the internal ticket for the team
