remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
GitHub no longer accepts account passwords for Git over HTTPS.
Exact message you may see
Support for password authentication was removedPlease use a personal access token instead
Seen on:
Git
Meaning
Use a personal access token (fine-grained or classic), the GitHub CLI / Git Credential Manager, or SSH keys.
Common causes
- Using your GitHub password in a git prompt
- Old scripts with user:password in URLs
⚡ Quick fix
- Create a token (Settings → Developer settings → Personal access tokens) and use it as the password
- Run gh auth login
- Switch the remote to SSH
Detailed fix by platform
Git
git remote set-url origin git@github.com:owner/repo.git
How to diagnose
- Method — HTTPS with password?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Git
- unfinished merge fatal: You have not concluded your merge (MERGE_HEAD exists). Please, commit your changes before you merge.
- rebase in progress fatal: It seems that there is already a rebase-merge directory, and I wonder if you are in the middle of another rebase.
- kex_exchange_identification kex_exchange_identification: Connection closed by remote host
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026