[BUG] OAuth error: listen EACCES: permission denied 0.0.0.0:54545

Status Fixed / completed
Maintainer reply ✓ Yes — igorkofman
Activity 6 comments · opened Jun 9, 2025 · closed Jun 15, 2025
💡 Likely answer: A maintainer (igorkofman, collaborator) responded on this thread — see the highlighted reply below.

Environment

  • Platform (select one):
  • [x] Anthropic API
  • [ ] AWS Bedrock
  • [ ] Google Vertex AI
  • [ ] Other: <!-- specify -->
  • Claude CLI version: 1.0.17
  • Operating System: Windows 10
  • Terminal: Git bash

Bug Description

I successfully initiated claude, used it for a few days, and then /logout to switch to a different account, upon running claude again and selecting the "Anthropic Console account" login method, it did not give me a new link to the console page. Tried re-installing to no avail.

Steps to Reproduce

  1. /logout
  2. claude

Expected Behavior

Be presented with a new link to open the console page

Actual Behavior

Prompted by the claude CLI binary: OAuth error: listen EACCES: permission denied 0.0.0.0:54545

Additional Context

!Image

View original on GitHub ↗

6 Comments

igorkofman collaborator · 1 year ago

We don't currently support git bash as a terminal.
Could you try again using WSL?

imding · 1 year ago
We don't currently support git bash as a terminal. Could you try again using WSL?

Hey thanks for the answer, I will give WSL a try.

However, it did work after I downloaded and installed it the first time, is there no way I can reset all the side effects created by the first initialisation?

igorkofman collaborator · 1 year ago

We are working on Windows support without WSL - sorry if you're having issues with it in the meantime.

NewSunSEO · 1 year ago

I tried for HOURS to get Claude Code to work on Windows 11 Pro. WSL also, but I couldn't spend more time trying... Had ChatGPT & Claude Desktop trying to get it work too... Wasted over 12 hours trying... Hopefully it works better on Windows soon...

nikkoxgonzales · 1 year ago
github-actions[bot] · 1 year ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.