git authentication ai_generated true

remote: Support for password authentication was removed. Please use a personal access token instead.

ID: git/credential-rejected

Also available as: JSON · Markdown
90%Fix Rate
92%Confidence
50Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
2 active — — —

Root Cause

Git HTTPS authentication failed because password-based authentication was deprecated by major hosts (GitHub, GitLab, Bitbucket). A personal access token or SSH key is required instead.

generic

Workarounds

  1. 92% success Generate a personal access token and use it as the password 
    Generate a PAT on the platform (GitHub: Settings > Developer Settings > Personal Access Tokens). Use the token as the password when prompted. Store it with: git config --global credential.helper store (or cache).
  2. 90% success Switch to SSH-based authentication 
    Generate SSH key: ssh-keygen -t ed25519. Add to agent: ssh-add ~/.ssh/id_ed25519. Add public key to the platform. Change remote: git remote set-url origin [email protected]:user/repo.git

Dead Ends

Common approaches that don't work:

  1. Repeatedly entering the same username/password when prompted 95% fail

    Password authentication is permanently disabled on the remote; no password will be accepted regardless of correctness

  2. Clearing the credential cache expecting it to fix the issue 85% fail

    The problem is not cached bad credentials; the authentication method itself (password) is no longer accepted by the server

Error Chain

Leads to:
Preceded by:
Frequently confused with: