GitHub 'Password Authentication Was Removed' Error
Fixed in latest version macOS, Windows, Linux Updated November 13, 2026Based on 4 user reportsHow we research
Quick answer
GitHub no longer accepts your account password for Git over HTTPS. Use a personal access token (or sign in through GitHub CLI or Git Credential Manager) wherever Git asks for a password.
Most likely fix: Create a token and use it as the password
How to fix it
Try these in order — the most common fix is first.
1. Create a token and use it as the password
- Open GitHub > Settings > Developer settings > Personal access tokens
- Create a fine-grained token (github_pat_...) with access to the repository and Contents: read and write, or a classic token (ghp_...) with the repo scope
- When Git asks for a password, paste the token
Did this fix it?2. Clear the stale cached credential
- macOS: open Keychain Access, search github.com and delete the entry
- Windows: Control Panel > Credential Manager > Windows Credentials > remove git:https://github.com
- Run git push again and enter the token when prompted
Did this fix it?3. Let GitHub CLI or Git Credential Manager handle login
- Install GitHub CLI and run gh auth login, choose HTTPS and sign in through the browser
- Or install Git Credential Manager, which caches the token so you are not prompted every time
Did this fix it?4. Authorize the token for SAML SSO organizations
- Open Settings > Developer settings > Personal access tokens
- Next to the token click Configure SSO and Authorize for the organization
Did this fix it?5. Switch the remote to SSH
- Add an SSH key to your account
- Run git remote set-url origin git@github.com:OWNER/REPO.git
Did this fix it?
Symptoms
git push or clone over HTTPS fails with 'remote: Support for password authentication was removed' or 'Invalid username or password' and 'Authentication failed'.
Why it happens
- Git over HTTPS only accepts personal access tokens, not the account password
- An old password is cached in the OS keychain or credential manager
- The token has expired or lacks the right scope/repository access
- The organization uses SAML SSO and the token is not authorized for it
This guide also covers
- support for password authentication was removed
- github authentication failed git push
- github personal access token password
- remote invalid username or password github
Still not working?
If GitHub keeps failing, you're not alone. See every GitHub problem users report or the alternatives people switch to.
Need a custom web app or internal tool? Our small team builds it, on your domain or hosted by us. Price agreed together.
Get a quoteOther GitHub errors
- GitHub Permission Denied (publickey) Error
- GitHub Push Rejected: Updates Were Rejected (Non-Fast-Forward)
- GitHub Push Blocked: Repository Rule Violations (GH013 / Secret Detected)
- GitHub Push Rejected: File Exceeds 100 MB Limit
- GitHub 'Permission Denied' or 403 When Pushing Over HTTPS
- GitHub Locked Out: Lost 2FA Device or Recovery Codes
- GitHub Actions Workflow Stuck in Queued / Waiting for a Runner
- GitHub Actions: 'Recent Account Payments Have Failed or Spending Limit Needs to Be Increased'