Bitbucket Authentication Failed on Git Push

How to fix it

Try these in order — the most common fix is first.

1. 1. Remove the cached credential

   Copy steps
   1. macOS: Keychain Access, search bitbucket, delete
   2. Windows: Credential Manager > Windows Credentials, remove git:https://bitbucket.org
   3. Run git push again and enter a fresh API token
   Did this fix it? Yes No

2. 2. Use an API token with the right scopes

   Copy steps
   1. Create it under Atlassian account settings > Security > API tokens with scopes
   2. Include repository read and write permissions
   3. Check the expiry date you chose
   Did this fix it? Yes No

3. 3. Switch the remote to SSH

   Copy steps
   1. git remote set-url origin git@bitbucket.org:<workspace>/<repo>.git
   2. Add your public key under Personal settings > SSH keys
   Did this fix it? Yes No

4. 4. Check 2FA and account

   1. Confirm you are on the account that has access to the workspace and repository
   Did this fix it? Yes No

Symptoms

remote: Invalid credentials, fatal: Authentication failed for https://bitbucket.org/..., or the credential prompt keeps returning.

Why it happens

• Old app password cached in the OS credential store
• Password login no longer accepted for git
• API token missing repository read/write scope
• Token expired
• Wrong username format

This guide also covers

• bitbucket authentication failed
• bitbucket git push authentication failed
• bitbucket invalid credentials

Other Bitbucket errors

• Bitbucket Permission Denied (publickey)
• Bitbucket App Passwords Deprecated: Switch to API Tokens
• Bitbucket Pipelines Build Minutes Exceeded
• Bitbucket Pipeline Stuck or Queued
• Bitbucket Pipeline Exceeded Build Time Limit
• Bitbucket Repository Over the Size Limit
• How to Cancel Bitbucket Subscription