Hi Vercel Community,
I'm experiencing a Production deployment authorization issue with the Vercel CLI. I would appreciate help identifying the cause and finding a safe resolution.
Environment
- Vercel plan: Hobby
- Team role: OWNER
- Vercel CLI version: 63.1.2
- Local Node.js version: 24.15.0
- Operating system: Windows / PowerShell
- Git provider: GitHub (connected successfully)
- Production branch: main
- Project configuration: Monorepo subdirectory, verified
All account names, project identifiers, repository names, and team identifiers have been intentionally omitted for privacy.
The Problem
When attempting a Production deployment from a locally linked Git worktree, I run:
npx --yes vercel@63.1.2 deploy --prod --scope [TEAM_SLUG_REDACTED]
The CLI returns:
Error: Not authorized
However, Preview deployment from the same project succeeds.
What I've Already Verified
- The Vercel CLI is authenticated successfully.
- The correct team and project are selected.
- My team role is OWNER.
- The GitHub account is connected to Vercel.
- The Git commit author is associated with the connected GitHub account.
- Project inspection succeeds.
- Listing Production deployments succeeds.
- Listing Production environment variables succeeds.
- No conflicting CLI authentication environment-variable overrides were found.
- The Production branch and Root Directory are configured correctly.
- The existing Production deployment remains READY and unchanged.
Questions
- What could cause Production deployment creation to return "Not authorized" when Preview deployment and Production read operations work?
- Could this involve CLI token permissions, Git identity verification, deployment authorization policies, or Hobby plan restrictions?
- Is there a safe way to identify the specific authorization failure or obtain a more detailed error code without repeatedly attempting Production deployments?
- What is the recommended solution without changing the existing Production deployment or pushing unrelated changes to the main branch?
The project has active Production infrastructure, including Queue consumers. I want to avoid accidental disruption during troubleshooting.
Any guidance from Vercel staff or experienced community members would be greatly appreciated.
Thank you!