nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

git push fails authorization while git clone works.

greza

Running on Linux.

I have a repository that I am the only user, so I am the admin with all the permissions.

I have set up access through SSH with SSH keys as was specified in the documentation. I am able to run git clone without any errors, but git push ends up with

---

fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

---

When running with ssh -vvv as suggested in one of the troubleshooting articles I can see
Authenticated to bitbucket.org (xxx:22) using "publickey".

closely followed by

Unauthorized

Any suggestion is greatly appreciated
Thank you

Accepted answers

Peter_DevSamurai

Hi Greza,

It might be that your SSH key is likely configured with read access (cloning) but restricting write operations (pushing), possibly it being added as a repository access key instead of a personal SSH key.

A) You can try few solutions below:

Verify Key Placement: Check if your SSH key is added to your personal account settings rather than the repository's access keys. Personal keys tie directly to your user permissions, which include full admin rights for pushes.
Test SSH Connection: Run ssh -T git@bitbucket.org to confirm it greets you with your username (e.g., "authenticated via ssh key"). If it does, the issue is likely authorization-specific.
Remote URL Check: Ensure your remote is set to git@bitbucket.org:yourworkspace/yourrepo.git (use git remote -v to verify).

Personal resolution (for 1 key and 1 account)

Go to your Bitbucket account settings -> SSH keys (under Security) and ensure your public key is added there. If not, add it following the provided guide below.
If the key is listed under the repository's settings -> Access keys, remove it from there -> Access keys are meant for CI/CD or read-only scenarios and can cause "unauthorized" errors for user pushes.
Restart your SSH agent if using one (eval "$(ssh-agent -s)" then ssh-add ~/.ssh/yourkey).
Try pushing again. If it persists, capture full logs with GIT_SSH_COMMAND="ssh -vvv" git push and share for more help.

You can read further in these guides:
- Troubleshoot SSH issues

- Set up personal SSH keys on Linux

Best,

Peter

All comments

Peter_DevSamurai

Hi Greza,

A) You can try few solutions below:

Verify Key Placement: Check if your SSH key is added to your personal account settings rather than the repository's access keys. Personal keys tie directly to your user permissions, which include full admin rights for pushes.
Test SSH Connection: Run ssh -T git@bitbucket.org to confirm it greets you with your username (e.g., "authenticated via ssh key"). If it does, the issue is likely authorization-specific.
Remote URL Check: Ensure your remote is set to git@bitbucket.org:yourworkspace/yourrepo.git (use git remote -v to verify).

Personal resolution (for 1 key and 1 account)

Go to your Bitbucket account settings -> SSH keys (under Security) and ensure your public key is added there. If not, add it following the provided guide below.
If the key is listed under the repository's settings -> Access keys, remove it from there -> Access keys are meant for CI/CD or read-only scenarios and can cause "unauthorized" errors for user pushes.
Restart your SSH agent if using one (eval "$(ssh-agent -s)" then ssh-add ~/.ssh/yourkey).
Try pushing again. If it persists, capture full logs with GIT_SSH_COMMAND="ssh -vvv" git push and share for more help.