xoris Hi Vercel team, Just following up on my question, as it’s been about a week without a response. We’re currently blocked on deploying our private beta because we need to confirm whether the first deployment of an existing, preconfigured project can overwrite its saved Next.js project settings. Could someone from the Vercel team clarify this behavior, or point us to the relevant official documentation? Even a brief confirmation would be very helpful. Thanks in advance!

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

Amy Egan Hey @hal-8981. Are you trying to report a security issue you uncovered? Or are you looking for something more like a security review for your project? I want to make sure I direct you to the right place

Haris Loganathan @amyegan The message was made by my AI agent. It was regarding the vulnerable PHP version, which as I understands, is fixed from vercel, with the node.js version. We just need to make a new deployment and update our security messures.

Ceosachin Release update: with the owner’s explicit authorization, we created one normal GitHub-source production deployment on the same existing project from the exact already-validated source commit 9af7b071ca405253ecd0b9dbfd1a1b1f5085bc27. New deployment dpl_8iZpQoWyQLv9pzSaR7MPM7m9Bji1 is READY/PROMOTED. The custom domain and project targets.production now both reference this deployment. Authenticated live UI, continuous typing/caret, nullable GSTIN and read-only Customer regressions passed. No forced alias, hidden metadata, project setting changes or Backend changes were used. The original FE46 art

Amy Egan A report through vercel.com/abuse is the right way to report this kind of thing. Do you have a ticket number I can check on?

Lindsay 9596 01555166 is the case number, thanks for your help @amyegan

Lindsay 9596 Bumping this as I am yet to receive a response @amyegan

Amy Egan Hey @paulmain79. Do you have a support case open? The community isn't able to issue refunds. That kind of thing is limited to the support team. If you don't have a case yet, please open one at vercel.com/help so the support team can assist!

Paulmain79 Hi Amy, thank you so much for coming back to me, and sorry for the slow reply. I've now opened a case: #CSE_01iu4vykeYDA9JVJ (Billing > Refund Request, Paul Main's projects, Pro). The case has the full picture: how the Preview build costs grew from May to October as our automated coding agents scaled up, the October Build CPU figure, and the three changes we've made (an ignoreCommand, on-demand Previews and Spend Management). I've had a lot of automated replies while trying to get this looked at, so I'd be really grateful if a member of the Billing team could take a look personally. We're a sm

Cv8p6d6gyv 4992 Hello Vercel team, I’m following up on this unresolved issue. OAuth authentication succeeds, but list_teams returns an empty list and requests to my existing Pro team return HTTP 403. Could Vercel Staff confirm whether this is a known MCP OAuth team-scope issue and advise on the supported fix? Please note that I do not authorize any changes to my production project, DNS, CARNET configuration, or GitHub main branch. Thank you.

Fededelrincon Fixed! The problem is network reachability between Claro Argentina and part of Vercel's IP range. I tested from Claro (home and mobile) during an outage: 216.198.79.1 and 216.198.79.65 → connection timeout (ports 443 and 80) 64.29.17.1 and 76.76.21.21 → OK (200) My domain uses Vercel DNS, which was returning only the 216.198.79.x addresses, so Claro users couldn't reach the site at all. Workaround: I added manual A records in Vercel DNS (@ and www → 76.76.21.21). Vercel serves those instead of the automatic ones, and once DNS caches expired (~30 min), the site worked again for Claro users with

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.

system Thank you for bringing this to our attention. To ensure this is investigated with the necessary priority and privacy, please report all security-related concerns, potential exploits, or abuse directly to the Vercel Security Team. Please submit your report here: vercel.com/abuse Reporting via this official channel is the fastest way to reach our security engineers and ensures that sensitive information is handled in a secure environment rather than a public forum.