Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix 403 PERMISSION_DENIED on auth login in New York [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#25869•Fetched 2026-04-24 06:13:43
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
johnjiamzhong-projectjohnjiamzhong-project
Participants
johnjiamzhong-projectjohnjiamzhong-project
Timeline (top)
labeled ×1

Error Message

API Error: The caller does not have permission status: PERMISSION_DENIED

RAW_BUFFERClick to expand / collapse

What happened?

Environment

  • OS: Windows 11
  • Gemini CLI version: 0.39.0
  • Node.js version: (运行 node --version 填入)
  • Location: New York, US

Problem

Running gemini auth login returns 403 PERMISSION_DENIED immediately. The OAuth flow does not complete. No browser window opens.

Error

API Error: The caller does not have permission status: PERMISSION_DENIED

Steps to reproduce

  1. Install @google/gemini-cli globally via npm
  2. Run gemini auth login
  3. Error appears immediately

Expected behavior

OAuth login should complete successfully.

What did you expect to happen?

The authentication flow should open a browser window for Google OAuth login and complete successfully, returning an authenticated session.

Client information

│ About Gemini CLI │ │ │ │ CLI Version 0.39.0 │ │ Git Commit 398f78dca │ │ Model Auto (Gemini 3) │ │ Sandbox no sandbox │ │ OS win32 │ │ Auth Method Signed in with Google ([email protected]) │ │ Tier Gemini Code Assist in Google One AI Pro

Login information

Google Account

Anything else we need to know?

The error occurs immediately when running gemini auth login without any browser window opening. Reinstalling the CLI did not resolve the issue.

extent analysis

TL;DR

The most likely fix is to check and potentially reset the authentication method or credentials used by the Gemini CLI.

Guidance

  • Verify that the Google Account credentials are correct and have the necessary permissions for the Gemini CLI.
  • Check if there are any issues with the OAuth flow configuration or if the gemini auth login command is being blocked by any security software or firewall rules.
  • Try signing out and then signing back in with the Google Account to refresh the authentication tokens.
  • Consider resetting the Gemini CLI configuration to its default state to rule out any misconfiguration.

Notes

The issue may be related to the authentication method or credentials used by the Gemini CLI, but without more information about the specific error or the configuration, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Try signing out and then signing back in with the Google Account to refresh the authentication tokens, as this may resolve any issues with expired or invalid authentication tokens.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

OAuth login should complete successfully.

#api#ssr#memory leak#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING