⌘K
Mr Robot 655 btw is deploying a minecraft bot against policy?
Amy Egan Thanks for sharing the project name. I think that's actually be why you're getting an error on the build. VCR's push path doesn't want to accept the project slug with an underscore. Can you try removing the underscore or replacing it with a dash and let me know if that makes a difference?
Mr Robot 655 Thank you Amy Egan, Thank you so much for the help! I changed the project name to use a dash instead of an underscore, and it worked! The daemon deployed successfully and my Minecraft bot is finally running. 😭🙏 Really appreciate you taking the time to look into this and point me in the right direction. I did not expect a reply but vercel actually reached out and would recommend vercel to others as well.
Drahmadadelawad Update on the same TEST deployment: We have now confirmed through the authenticated Vercel dashboard and store metadata that its connected private Blob store is suspended with `usageQuotaExceeded: true` and status `limits-exceeded-suspended`. The displayed Sep 22–Oct 22 usage window shows 2,968 / 2,000 Blob Advanced Operations. The dashboard describes this as usage across Blob stores; we are not attributing all operations to this deployment. This is Vercel Blob usage, not Firebase quota. We are evaluating an ownership-verification-only approach: one project routing rule matching the exact original deployment hostname and the exact Google-provided HTML verification filename, serving an owner-controlled public static verification file through a rewrite. Application paths, the existing deployment build, deployment protection and the primary Stable TEST alias would be preserved. Is this officially supported for that existing generated deployment URL? With Blob currently suspended, is there an approved no-cost verification-file path or another official ownership/diagnostic option that preserves those constraints? No private store was made public, no second store was created to bypass limits, no paid plan or trial was enabled, and no routing change or deployment has been made. The application remains on hold while the Google warning is unresolved. No additional Google report has been submitted.
Amy Egan Google offers multiple ownership verification options through simple site additions that do not require DNS changes. You can use whichever of them makes sense for your educational test deployment. Vercel does not control Google's website ownership verification process. https://support.google.com/webmasters/answer/9008080?hl=en
Eddier Naranjo +1 for this private beta. I'm building Eddier Operator, a private operations platform running on my own VPS. One of its workers monitors infrastructure health using isolated, least-privilege adapters. I need to monitor a Vercel project without giving the observer any ability to deploy, modify settings, delete resources, or perform other write operations. My initial requirement is intentionally narrow: Project: maximo-retorno-control-center Required permissions: read:project read:deployment Vercel Support confirmed to me that project-scoped Personal Access Tokens currently still grant both read and write access, so they do not satisfy this security requirement. The integration is already designed to reject broad personal Vercel tokens and will only be activated once a genuinely read-only Vercel App credential is available. I'd be very interested in joining the Sign in with Vercel API Permissions private beta if additional participants are being accepted. Thank you, Eddier Naranjo
Amy Egan Hi @blaswan and @eddiernaranjo . We're not adding new teams to the private beta at the moment, but keep an eye on the changelog. The team will make an announcement about public beta when they're ready for more teams to try it!
