starrdev Issue is resolved. Disregard

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.

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.

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.

laurentcoplet-3124 Hello Vercel MCP team, I'm experiencing a persistent authorization issue with the official ChatGPT–Vercel MCP integration. The connection correctly authenticates my Vercel account, recognizes my team and confirms my OWNER role. However: list_projects returns an empty list. get_project returns 404. list_deployments returns 403. get_deployment returns 404. I have already reconnected the integration and explicitly authorized the team, without success. The same account can successfully access and deploy the existing project using Vercel CLI. Vercel Support confirmed that MCP is currently in Beta a

Anshuman Bhardwaj Hi there, we're sorry, but there's no way to find the historical value of an environment variable.

Anshuman Bhardwaj Hi Julian, if I understand it correctly, your GitHub account was made with an Apple Private Relay email? But, you no longer have access to that email to login. If your GitHub is linked with another account and you want to relink it to this one, you can remove it from the Authentication Settings in the 1st account and then connect it to this one (given you can log into both of them).

Julian B I have access to the Apple Private relay email, the issue is that once I re-connected Github to another vercel made account. It disconnected the authenticated account that i originally made, so when I went to reauthenticate via the Github option. Vercel wants to verify via a code which sends to that Apple Private Relay email. Apple requires 'Sign in with Apple' apps to be given permission upon registering to become approved. Then you are able to forward emails to another account, for example. Incoming Apple Private Relay Email (Vercel Confirmation code) - Forward to - another personal email So

Julian B I also think that when my Vercel account was created via the Github option. It obviously registers the email address with Vercel, so Vercel is expecting that email to be able to login. If i change it on the Github side, It just causes more problems and disconnects the ability to receive any email whatsoever to authenticate the login.

system If you're having trouble deploying an Express app, this guide can help. vercel.com/guides/using-express-with-vercel You can also ask v0 for suggestions tailored to your own project setup.

Group-IB DRP Dear Vercel Support, Can we get your urgent assistance for the reported phishing on: alert-me.vercel.app Your urgent support is highly appreciated.

Group-IB DRP @anshumanb @pawlean can you please support in this report. We have submitted multiple reports on the abuse form.

Rampare99 Hi Vercel team, I'm following up on this thread, as it's now been over a week without any response. What's particularly concerning is that I've noticed several other users opening threads in recent weeks describing essentially the same situation: Hobby teams remaining permanently suspended even after the projects responsible for excessive usage have been removed. These reports also appear to be going unanswered. At this point, I'm not just asking for my own account to be reviewed. I'd genuinely appreciate some clarification on Vercel's policy: 1. Is a Hobby team suspension intended to be perma

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

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.